Post reply

CREATE TABLE is creating System tables

  • October 23, 2007 at 2:53 pm

    #73781

    I have a SQL 2000 Enterprise SP3 test server, and whenever I try to create a new table on any of its databases, the table will be created as a System table rather than a User table. It doesn't matter whether I use T-SQL, SQLEM, or DTS -- the result is always a System table. I even created a new database on the server and tried to create a new table on it, and it was created as a System table. This server hasn't always exhibited this behavior. The behavior has been introduced fairly recent (within the past month or so). Has anyone ever seen this?

  • October 23, 2007 at 7:48 pm

    #744721

    somebody ran this command:

    --Turn system object marking on

    EXEC master.dbo.sp_MS_upd_sysobj_category 1

    after that is run, all commands that create objects in SQL 2000 are system objects. this is fine if you were adding your own stuff, like sp_who3 or something, but you are supposed to turn off system marking after you are done.

    to stop that behavior run this command:

    --Turn system object marking off

    EXEC master.dbo.sp_MS_upd_sysobj_category 2

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • October 24, 2007 at 8:58 am

    #744999

    Worked like a champ - thanks!

    I'm wondering if one of our apps (namely What's Up Gold) might have done this during installation? I certainly didn't do it and I doubt seriously that anyone else here would have either, at least not explicitly.

    Thanks again!

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply