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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-03-18 : 09:55:09
|
| David writes "We recently upgraded SQL Server 7 to SQL Server 2000. We have about 10 DTS Packages they we schedule to run several times a week. Two of the packages were accessing a FoxPro free table using ODBC. Every once and a while the ODBC DSN would corrupt, and we would just recreate it and the package would continue to run fine.The same thing happened again right after we upgraded the SQL server to 2000. We were able to recreate the DSN and get the package running again, but we can no longer edit the package to make changes.We also upgraded the SQL tools to SQL server 2000 at the same time we upgraded the Server. I know that you can have problems if you do not have the same version tools as the server. I am at a loss, and I would rather not have to recreate these DTS packages from scratch.Thank you,David Fekke" |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-03-18 : 11:45:24
|
| What do you mean by can't edit? Is it giving you any specific error messages? Do you not see the list of packages in EM? Are you trying to edit the packages from a workstation or the server they run on? We need a little more information to help you out.Jeff BanschbachConsultant, MCDBA |
 |
|
|
|
|
|
Why can't I edit DTS packages since I upgraded to SQL 2000.