sounds good. I'll look into it as well. I'm managing to trudge through this
blasted DTS export wizard for the most part now after tinkering around...
waste of time! Anyone know if sql server 2005 has more accessibility built
in the tools?
Justin
Hi Justin,
I could be wrong, but I'm fairly sure that there are configuration options in the export wizard for CSV files that allow you to specify string delimiters. I thought the default was double quotes. Thus, theoretically string values containing commas should be no problem. It generally only becomes a problem when you have string values with double quotes in them. But still, I might be thinking of something else. Next time I'm at a PC with the SQL Server Client Tools on it, I'll fire up the import and export wizard and see.
All the best,
David
-----Original Message-----
From: program-l-bounce@xxxxxxxxxxxxx [mailto:program-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Justin Daubenmire
Sent: 07 September 2005 07:00
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: sql server tables and DTS
Thanks David. I've done that before.... the export data from the table to a
csv file and create a script for the table and create the table on the other
db and then import the csv file. It works, however, not if the exported data
is varchar fields with commas in them and you go to import the data via the
dts import wizard grin.
I'm with David here folks, if there is an easy way to do this, or a better accessible way, please let us know.
Thanks.
Justin
----- Original Message ----- From: "David Lant" <david.lant@xxxxxxxxxxxx>
To: <program-l@xxxxxxxxxxxxx>
Sent: Wednesday, September 07, 2005 12:10 PM
Subject: [program-l] Re: sql server tables and DTS
Hi Justin,
Last time I did this, I used the DTS wizard, and struggled through the inaccessibility problems. Not pleasant, but achievable if you're prepared to drink lots of coffee and grind your teeth. <grin>
The other method I use, is to get one of our DBAs to do it. But that probably isn't an option... <smile>
A final, and slightly long-winded way is to do it in two halves. Right click the table, and choose the generate script option to script the table creation. Then, right click the table again, and choose the export wizard, which is basically the same DTS wizard as before. But this time, simply choose to export the data to an Access database or some other external format. Then you can go to the other machine, run the table script to create the table, and finally import the data from the Access database.
None of these are ideal, I admit. But you might be able to manage somewhere along the way. If someone does have an alternative method that is completely accessible, I'll be interested too.
David Lant
I.T. Consultant Consultancy & Development ICT Services Tel: (01392) 382464
Devon County Council accepts no legal responsibility for the contents of this message. The views expressed do not reflect those of Devon County Council.
-----Original Message----- From: Justin Daubenmire [mailto:justind@xxxxxxxxx] Sent: 07 September 2005 15:42 To: program-l@xxxxxxxxxxxxx Subject: [program-l] sql server tables and DTS
All.
Simple task but not knowing if there is an accessible way of doing it.
Have
a table that I need to copy it and the data over to a separate sql server
2000 db on a different server. Both dbs and tables are in sql server 2000.
I am aware that I can use the DTS and create a package, however, the DTS package utility in enterprise manager doesn't seem all that accessible to me.
What method do you all use to copy a table and its data over to a new server/db?
Again, both dbs and tables are sql server 2000 and just needing to do a simple copy from db 1 over to db 2 on a different server.
Justin
** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq ** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq