SQL Help

gigabyte1024

[H]ard|Gawd
Joined
Mar 10, 2001
Messages
2,027
I need to copy data from an ODBC source to a SQL database.
Anyone willing to help me out?

I think this can be done in multiple ways using straight sql or a dts package, but I know nothing about either.

Thanks.
 
The DTSWizard will let you do it pretty quickly.

You don't ask a specific question, so I'm not sure what help you're looking for.
 
DTS would probably be the quickest and most efficient way to do it.

 
The ODBC I need is not listed in the "Data Source" drop down.
It is installed and listed under the User DSN section of the Data Sources control panel applet.

I came up with this as a connection string, does it look right?
"Dsn=SOTAMAS90;Driver={MAS 90 32-Bit ODBC Driver}"

I need a query to copy specific tables, I need to copy about 8 different tables how do I do that?

Thanks again.
 
Your connection string looks syntactically correct, but I have no way to know if represents your semantic intent.

Just run the DTSWizard. It allows you to specify a table or a query.
 
I put this in as a query and DTS Wizard keeps crashing.

SELECT * FROM AR1_CustomerMaster
 
I wish I could help you, but with so little information to go on, it's not easy.
 
I don't know what else to provide, what do you need to know?

:confused:

I think I'm close to having it work, but like I said DTS Wizard crashes.
I put in the query and click parse and it says it's valid.
I click next and the next page shows, but it says
"SQL Server Import and Export Wizard has encountered a problem and needs to close."
There is no error number displayed.
There is an info entry in the app event log "Starting up database SysTemp"

There is an error entry from yesterday but not today
"Faulting application dtswizard.exe, version 9.0.1399.0, stamp 434f5e2a, faulting module pvkiw32.dll, version 3.21.0.1, stamp 3c48907d, debug? 0, fault address 0x00001c00."

edit: it seems that dll has to do with the odbc driver and not sql.
 
I don't what? Have to use Access a middle man?
It seems the ODBC driver that I'm forced to use isn't compatible with SQL 05.

If you have another idea, I'm all ears.
 
Back
Top