August 17, 2009 at 12:51 pm
Hi all -
I am having a bit of a problem with the DTS designer in SQL Server 2000 SP4 Enterprise Administrator...
I have a bunch of DTS packages that copy data from an IBM iSeries to our SQL Server. Many of these DTS packages have been in place for some time now - and all continue to run as usual. However, if I attempt to "design" these packages now (to update some of the transform options for example) the MMC hangs at 100% CPU, and I am not able to look at the properties for that particular portion of the package.
These packages are all using the iSeries Access for Windows ODBC driver. I thought there may be something wrong with the driver, but as I mentioned earlier, the DTS jobs continue to run properly - and I can use the same ODBC (system) connection from within Excel without any issue (from the same SQL Server box).
I am not sure what is causing this... has anyone experienced a similar symptom?
TIA -
David
August 23, 2009 at 7:42 am
Hi David,
I don't know why you are using the same SQL Box to design the DTS Packages.
You can try this, Install SQL Server Client tools on some other test server, then connect to your SQL Box and then try opening DTS Designer, it might help.
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
August 23, 2009 at 4:11 pm
Thanks for the reply!
I guess we have just always used the local tools on the SQL Server to create / edit DTS packages.
I am inheriting this system, so there are a lot of things like this that I am becoming acquainted with.
Since I am still pretty novice to SQL Server, my question would be that if I am editing DTS packages on that server from my local workstation, would I run into issues with ODBC connections and such that are currently only on that SQL Server? Would I need to have thise types of items setup exactly the same on my workstation?
Thanks!
David
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply