Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2005-03-07 : 09:56:52
|
| Before I go down the road of using DTS for the first time, I need to know that it's advantages in my situation is going to be significant enough. Does DTS have a clear performance gain over SQL INSERT?My source and Target are boh SQL DB's. The source has a Name column with name and surname. My destination db has first name and last name. So I need to apply some logic (splitting the name into first name and last name) before inserting data into the new db. I have to apply many different kinds of logic infact in different areas before populating the new db.Will this minimize the performance gain DTS brings? Should I just stick with using a VB.NET app? |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-03-07 : 12:53:36
|
| sounds like DTS would be a good choice here. DTS is an extract, transform and load tool. It sounds like you are doing all three of those tasks here.As far as speed goes, an INSERT from a SELECT is going to be faster than DTS. But, if you have to do a lot of data transformation, the DTS process may be easier to work with (and change). Debugging DTS packages is sometimes tricky though. www.sqldts.com is a good resource for DTS information if you are just getting started.-ec |
 |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2005-03-07 : 12:57:43
|
| Probably the fastest would be to use bcp with a query that splits up the field to export to a file then another bcp to import.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
ashishnaik1
Starting Member
5 Posts |
Posted - 2005-03-07 : 15:28:33
|
| I agree with eyechart. For DTS is good for ETL - the scenario you have. |
|
|
|
|
|
|
DTS faster than SQL INSERT