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 |
|
snake9284
Starting Member
10 Posts |
 Posted - 2007-11-20 : 11:33:36
|
| Some Background information first:We are currently in the process of consolidating all of our production databases into a single db with conformed dimensions. As part of the consolidation process we are taking the existing DTS packages and creating stored procedures to replace them. This is being done because we are going to be upgrading our servers to SQL Server 2005 where we would not be able to edit the DTS packages if anything were to go wrong. My question is in regards to the DTS packages that pull information from other datasources (Oracle, DB2, Access) and those that process Dimensions and Cubes. 1. Would it be best to leave these processes as DTS packages and then create SSIS packages when we migrate to 2005 or should I create linked servers for the datasources?2. I know that we can process cubes with VbScript, are there any other options to the cube and dimension processing tasks? |
|
|
Hommer
Aged Yak Warrior
808 Posts |
Posted - 2007-11-21 : 09:24:44
|
| You are right in saying that in sql05 the DTS created in sql2k are not editable.However, they will run under 05 as is. In the long run, you should replace them with SSIS thou.I am not sure how you can replace DTS with sp.You don't need linked servers for those data sources. And, sql05 has SSAS that will process cubes. Check it out. |
 |
|
|
snake9284
Starting Member
10 Posts |
Posted - 2007-11-21 : 11:01:41
|
| Thanks for the reply Hommer. I was just trying to come up with some possible ways to eliminate the DTS packages altogether while I'm consolidating the db's. A lot of the steps in the packages I was able to replace by creating a stored procedure for them. I guess that leaving some tasks as DTS packages isn't bad as long as I wouldn't have to create the SSIS packages right away when we migrate to 2005 in a couple of months. I'm glad that we've decided to do both of the projects at the same time. *said with a hint of sarcasm* i'm looking forward to working with 2005, I've heard that AS is much better than its 2000 counterpart. The other big positive is the upgrade to the 64-bit server!!! Some of the jobs that we run now just seem to take way too long to complete on the current boxes. (All of them are 32-bit) |
|
|
|
|
|
|
SQL 2000 to 2005 DTS Questions