0 - 8 of 8 tags for lob

Hello All,
I am trying to insert a image in the DB. Follow is the DDL:
CREATE TABLE DB.Sample3
(
ID INT GENERATED ALWAYS AS IDENTITY(START WITH 1 INCREMENT BY 1),
Image BLOB(9000)
);
 
INS INTO DB.Sample3 values(,?B); (Trying to insert a image from the windows pictures)
SEL* FROM DB.Sample3;

Hi everyone.  I'm trying to load SQL server tables to Teradata14 using OleDB via TD's OleLoad tool.  I'm having trouble with attributes defined as VARCHAR(MAX) in SQL server - it seems that this is a LOB data type.  Here is the script that OleLoad is generating:

As most of you might agree, managing our collections of digitial pictures is becoming quite a challenge.  The number of photos continues to increase and now includes pictures from cameras as well as multiple mobile devices.  And to add to my troubles, I find that I have duplicate copies in different folders and on different computers.  Getting this organized is becoming a high priority.  Sure there are management solutions already available, but hey, we're tech people and it's more fun to try to build our own!  With the free Teradata Express database and some java coding, we have the right tools to get started.

This book provides reference information about BTEQ (Basic Teradata Query), a general-purpose, command-based report and load utility tool. BTEQ provides the ability to submit SQL queries to a Teradata Database in interactive and batch user modes, then produce formatted results.

In parts 1 and 2, we looked at how to load and retrieve large objects using Teradata BLOBs and CLOBs. In part 1, I put forward my unbreakable golden rule that you shouldn’t simply store Object Models as Large Objects. Rather, always map your objects’ attributes to columns in a table; don’t just serialize a bunch of classes and store them in a BLOB.

In part 3, I present another of my unbreakable golden rules; which is “Rules were made to be broken”. The focus of this article is how to serialize and persist (store) an Object Model into a BLOB on Teradata and reinstate it.

In Part 1, we looked at what Large Objects are and some tactics that we could employee to load them into Teradata. As I stated back in part 1, loading large objects is great, but by itself is pretty useless. In this article, we will look at extracting Binary Large Objects from Teradata for inclusion in a web application.

But before we get to that, we need to know something about the large objects we will be dealing with.

Lately it seems like there has been quite a few questions relating to the use of Large Objects on the various Teradata forums. Mostly these revolve around the question of how do I get Large Objects into the database. So it seems like there is a bit of mystery surrounding Large Objects.

For myself, the mystery is just who is “Large” and to what does he (or she) “Object”? Perhaps "Large" objects to the veil of mystery being lifted which is what this series of articles is about - working with Large Objects.

In part 1, we will look at getting those Large Objects of yours into the Teradata. One way or another we will get them into Teradata, kicking and screaming if need be (however, it will be relatively painless, I promise) and we will do this despite any "Objections" "Large" may have.

Later in part 2, we will drag those Large Objects back out and use them in a web application.