Oracle to SQL Server

I've got a commercial Oracle database that I need to reverse engineer
to SQL server.
Using ER/Studio, I've generated the DDL for the tables, but one of the
lines references setting an image datatypes default to Empty_Blob, not
Null, and Query Analyzer gives me an error when it tries to interpret
that portion "Empty_Blob" of the DDL.
Any ideas how I should handle this?
CREATE TABLE abcdefg (
CRL image DEFAULT EMPTY_BLOB() NOT
NULL,
LAST_DOWNLOAD datetime NULL,
NEXT_DOWNLOAD datetime NULL,
SOURCE_URL varchar(1000) NULL,
THUMBPRINT varchar(60) NOT NULL
)
GO
--
HTH
Dale FyeI have no idea what EMPTY_BLOB is (maybe a user defined type?) but how about
'' instead.
--
Andrew J. Kelly
SQL Server MVP
"Dale Fye" <dale.fye@.nospam.com> wrote in message
news:OWcP3%23xnDHA.2244@.TK2MSFTNGP12.phx.gbl...
> I've got a commercial Oracle database that I need to reverse engineer
> to SQL server.
> Using ER/Studio, I've generated the DDL for the tables, but one of the
> lines references setting an image datatypes default to Empty_Blob, not
> Null, and Query Analyzer gives me an error when it tries to interpret
> that portion "Empty_Blob" of the DDL.
> Any ideas how I should handle this?
> CREATE TABLE abcdefg (
> CRL image DEFAULT EMPTY_BLOB() NOT
> NULL,
> LAST_DOWNLOAD datetime NULL,
> NEXT_DOWNLOAD datetime NULL,
> SOURCE_URL varchar(1000) NULL,
> THUMBPRINT varchar(60) NOT NULL
> )
> GO
> --
> HTH
> Dale Fye
>
>|||Dale,
There is no concept of EMPTY_BLOB in SQL Server. You can default the same to
NULL or as '' when using the same ...
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
"Dale Fye" <dale.fye@.nospam.com> wrote in message
news:OWcP3%23xnDHA.2244@.TK2MSFTNGP12.phx.gbl...
> I've got a commercial Oracle database that I need to reverse engineer
> to SQL server.
> Using ER/Studio, I've generated the DDL for the tables, but one of the
> lines references setting an image datatypes default to Empty_Blob, not
> Null, and Query Analyzer gives me an error when it tries to interpret
> that portion "Empty_Blob" of the DDL.
> Any ideas how I should handle this?
> CREATE TABLE abcdefg (
> CRL image DEFAULT EMPTY_BLOB() NOT
> NULL,
> LAST_DOWNLOAD datetime NULL,
> NEXT_DOWNLOAD datetime NULL,
> SOURCE_URL varchar(1000) NULL,
> THUMBPRINT varchar(60) NOT NULL
> )
> GO
> --
> HTH
> Dale Fye
>
>

Oracle not supported?

I installed de trial version of SQL Server 2005 Workgroup, then created a
small report using a Oracle Database.
In Visual Studio the report previews fine but after being deployed to SSRS
i't tells me that the data extension is not registered.
Is this a trial version issue or is the Oracle support for SSRS have to be
configured after instalation?
Juan Ignacio Herreralook at this page:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx
the workgroup edition support only data source against the same SQL Servre
installation only.
you can't directly access Oracle or any external source.
but... maybe you can create a linked server to your oracle database and
create your queries using the openquery SQL command.
the queries will come from your local server and not from your oracle
database.
"Juan Ignacio Herrera" <nacho(quitar)@.delta.com.gt> wrote in message
news:uQ8sNyvGGHA.3176@.TK2MSFTNGP12.phx.gbl...
>I installed de trial version of SQL Server 2005 Workgroup, then created a
> small report using a Oracle Database.
> In Visual Studio the report previews fine but after being deployed to SSRS
> i't tells me that the data extension is not registered.
> Is this a trial version issue or is the Oracle support for SSRS have to be
> configured after instalation?
> Juan Ignacio Herrera
>

Oracle drivers in connection managers

I am not seeing an option to use the OraOLEDB.Oracle driver when defining connections in ssis. This driver shows up in management studio when trying to create linked servers so I don't know why it wouldn't show up here. All the client tools are installed fine and the linked server works. Any ideas?This might be a novice answer, but are you sure the actual OLE driver is installed? I'm no Oracle expert by far, but the client and the actual driver that my Oracle dba gives for sql server installation are on seperate disks.|||Yes, the oledb drivers are installed. One important thing I failed to mention is that this is a 64 bit server. What appears to be happening is that even though we can create a linked server with the 64 bit oracle oledb driver, when you create a package in ssis it only lists the 32 bit native oledb drivers. I confirmed this by installing the 32 bit oracle client stuff as well and now the oracle oledb driver is listed in the drop downs. This seems a little absurd that ssis would only use the 32 bit drivers, can anyone explain this?|||

"The 32-bit SSIS Designer displays only 32-bit providers that are installed on the local computer. If you want to select a specific 64-bit provider to configure a connection manager, you must have the 32-bit version of the provider installed. However, you can still run the package in 64-bit mode in the development environment. Because the 32-bit and 64-bit versions of a provider have the same ID, the runtime selects the appropriate version to use based on the value of the Run64BitRuntime project property, which by default is True."

Found in this article....

http://msdn2.microsoft.com/en-us/library(d=robot)/ms141766.aspx

|||

Thanks for the info, that's a big help.

I understand why they did this but just like every other weird x64 quirk you have to spend hours digging through various documentation sources to even find a mention of it. Please just give us a comprehensive x64 guide instead of spreading stuff out in a thousand different places.