MS SQL 2000 extra tbs

[allida77]

I have installed the single user MS SQL 2000 on my machine. When I create a new table it automatically creates a bunch of sys tables. Is this necessary? Is there any harm in deleting them?

[whammy]

I'm not sure... but from what I've seen at work, all kinds of "sys" tables have been created as well (which I always just assumed were necessary - I don't have access to install that stuff as it's left up to our network admin - and I haven't installed it on my home machine).

I guess you could delete them, and see if it works (basic troubleshooting, lol)!

If not, you can just reinstall it and recreate the tables. But I have a feeling they are necessary. If noone else knows offhand, lemme know how it goes! :D

[fractalvibes]

Does it do this EVERY time you create a new table? I would think that there should be a group of system catalog tables, and these are updated when you create new tables, of course.

[aCcodeMonkey]

All,

The "sys" tables are SQL system tables used to store information and define the database structure. For Example sysobjects. contains the definititions for the physical structure of tables within each database. Sysusers contains account information pertaining to a specific database.

Take a look here for more information:
SQL System Table References (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sys_00_690z.asp)

Hope this helps.. :cool:

[whammy]

I don't think there can be any clearer explanation than there is at the link that aCcodeMonkey posted! So I'm going to close this thread.

allida77, if you have any further questions regarding this phenomenon, please feel free to create another post!

As you can see by the link that aCcodeMonkey provided, they are necessary, like I guessed.

I did learn some additional information from the link provided, though.

I love this forum. Sometimes when you think you are helping people you end up learning instead.

Bottom line: YES there is harm in deleting them. Don't do it! ;)
:D