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 |
|
patshaw
Posting Yak Master
177 Posts |
 Posted - 2009-01-23 : 07:17:13
|
| I was working on producing some code that would import legacy DTS packages between log shipping servers so, in case of failover, both servers would have matching DTS's. Both are running SQL Server 2005. To do this I initially produced some code that ran from the DR server. This code dropped the table 'sysDTSpackages' in the MSDB database and then did a select into from the same table on the source server to re-populate.While this appears to work perfectly well, all DTS's open and appear to function correctly, the 'sysDTSpackages' table is now a user table and not a system table when viewed through Management Studio.What do I need to change to make this table a system table once again?Thanks. |
|
|
patshaw
Posting Yak Master
177 Posts |
Posted - 2009-01-23 : 08:48:54
|
| A strange thing I have noticed is that when I look at the original table (the one that wasn't dropped) on the source server by running sp_help or querying sysobjects, this table is identified as a user table and not a system table but through MS it is viewed in the sytem tables folder and displays this way through the right-click/table properties. This seems to be consistent on all SQL Server instances. |
 |
|
|
|
|
|
System table now shows as user table