New Tables and Stored procedures are saving as System Tables

When I try to create a new table/stored procedure, MSDE is saving it as
system table/procedure. And this is happening to all the databases on that
instance.
I checked the sysobjects table. The new tables are saved as Type 'U'.
But their status is in -ve nos.
What I can do to fix that?
Hi
You should not rely on using the "FOR MS USE" objects/columns. What does
OBJECTPROPERTY(id,'IsSystemTable') return?
John
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:45F7565B-FC35-437E-88CC-30E896875DF0@.microsoft.com...
> When I try to create a new table/stored procedure, MSDE is saving it as
> system table/procedure. And this is happening to all the databases on that
> instance.
> I checked the sysobjects table. The new tables are saved as Type 'U'.
> But their status is in -ve nos.
> What I can do to fix that?
>
>

New Tables and Stored procedures are saving as System Tables

When I try to create a new table/stored procedure, MSDE is saving it as
system table/procedure. And this is happening to all the databases on that
instance.
I checked the sysobjects table. The new tables are saved as Type 'U'.
But their status is in -ve nos.
What I can do to fix that?Hi
You should not rely on using the "FOR MS USE" objects/columns. What does
OBJECTPROPERTY(id,'IsSystemTable') return?
John
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:45F7565B-FC35-437E-88CC-30E896875DF0@.microsoft.com...
> When I try to create a new table/stored procedure, MSDE is saving it as
> system table/procedure. And this is happening to all the databases on that
> instance.
> I checked the sysobjects table. The new tables are saved as Type 'U'.
> But their status is in -ve nos.
> What I can do to fix that?
>
>

new stored procedures created as type system instead of user

I am running SQL 2000 SP4. When I create a new stored procedure it is
being created as type system instead of user. How can I make it so
every new sp I create is type user instead of system? Thanks in
advance.Hi
"ginarunco@.hotmail.com" wrote:

> I am running SQL 2000 SP4. When I create a new stored procedure it is
> being created as type system instead of user. How can I make it so
> every new sp I create is type user instead of system? Thanks in
> advance.
>
Run DBCC TRACESTATUS ( 1717 )
If the flag is on, run
EXEC sp_MS_upd_sysobj_category 2
Check the SQL Server Startup parameters to make sure it doesn't turn this
trace flag on at startup.
John

new stored procedures created as type system instead of user

I am running SQL 2000 SP4. When I create a new stored procedure it is
being created as type system instead of user. How can I make it so
every new sp I create is type user instead of system? Thanks in
advance.
Hi
"ginarunco@.hotmail.com" wrote:

> I am running SQL 2000 SP4. When I create a new stored procedure it is
> being created as type system instead of user. How can I make it so
> every new sp I create is type user instead of system? Thanks in
> advance.
>
Run DBCC TRACESTATUS ( 1717 )
If the flag is on, run
EXEC sp_MS_upd_sysobj_category 2
Check the SQL Server Startup parameters to make sure it doesn't turn this
trace flag on at startup.
John
sql

new stored procedures created as type system instead of user

I am running SQL 2000 SP4. When I create a new stored procedure it is
being created as type system instead of user. How can I make it so
every new sp I create is type user instead of system? Thanks in
advance.Hi
"ginarunco@.hotmail.com" wrote:
> I am running SQL 2000 SP4. When I create a new stored procedure it is
> being created as type system instead of user. How can I make it so
> every new sp I create is type user instead of system? Thanks in
> advance.
>
Run DBCC TRACESTATUS ( 1717 )
If the flag is on, run
EXEC sp_MS_upd_sysobj_category 2
Check the SQL Server Startup parameters to make sure it doesn't turn this
trace flag on at startup.
John

New project - thinking of using Visual studio 2005

Hi
I've been developing sql server stored procedures for what seems forever,
right now I just use query analyzer.
I have a new project, and just for a chuckle I'm thinking of using Visual
Studio 2005 for my IDE instead of query analyzer, I'm still pretty much just
going to be creating sql server stored procedures (SQL 2K).
Does anybody have any hints, gotcha's or guidance on whether this is a good
idea, and if so any tips?
I've played around, and one thing I can't find, can I run a SQL and have a
nice output to grid option, like with query analyzer?
The main reason I want to use this, is for being able to put all my sql in a
project, and the integration with sourcesafe.
Thanks in advanceInstead of the 'full' Visual Studio, use the Sql Server Management Studio.
When you disable the 'Summary' tab at startup, it behaves more or less the
same way as ye olde QA, but a little better :)
Yes, you can still have grids and text output :)
Peter
"..." <...@.nowhere.com> wrote in message
news:ehgLtTgQGHA.4896@.TK2MSFTNGP10.phx.gbl...
> Hi
> I've been developing sql server stored procedures for what seems forever,
> right now I just use query analyzer.
> I have a new project, and just for a chuckle I'm thinking of using Visual
> Studio 2005 for my IDE instead of query analyzer, I'm still pretty much
> just going to be creating sql server stored procedures (SQL 2K).
> Does anybody have any hints, gotcha's or guidance on whether this is a
> good idea, and if so any tips?
> I've played around, and one thing I can't find, can I run a SQL and have a
> nice output to grid option, like with query analyzer?
> The main reason I want to use this, is for being able to put all my sql in
> a project, and the integration with sourcesafe.
> Thanks in advance
>|||There is more flexibility within visual studio itself wrt managing your
project (you can add more folders for managing DDL/DML scripts and such).
Typically I manage my project and the source control integration from within
VS and jump back and forth to management studio depending on the specific
task at hand (say building up and testing a specific set of queries within a
larger procedure). SQL management studio allows for source control
integration and projects but is slightly different. The overall impression
I
have gotten from the two is that the SQL management studio projects are
geared more toward DBA work where as VS is more for the DB developer.
HTH
--Tony
"Rogas69" wrote:

> Instead of the 'full' Visual Studio, use the Sql Server Management Studio.
> When you disable the 'Summary' tab at startup, it behaves more or less the
> same way as ye olde QA, but a little better :)
> Yes, you can still have grids and text output :)
> Peter
> "..." <...@.nowhere.com> wrote in message
> news:ehgLtTgQGHA.4896@.TK2MSFTNGP10.phx.gbl...
>
>