Showing posts with label diagram. Show all posts
Showing posts with label diagram. Show all posts

Monday, March 19, 2012

Cannot create diagrams in Upgraded SQL Server 2000 Database

Dear all,

I am trying to save a newly created diagram in SQL Server 2005 SP1.

The error message is:
-Beginning of pasted error message

===================================

Cannot insert the value NULL into column 'diagram_id', table 'adt_db.dbo.sysdiagrams'; column does not allow nulls. INSERT fails.
The statement has been terminated.
The 'sp_creatediagram' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. (.Net SqlClient Data Provider)

Program Location:

at Microsoft.VisualStudio.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DatabaseDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)

-End of pasted error message

The database I use has been upgraded from SQL Server 2000.

I am running in SQL Server 2000 Compatibility Mode (80) but changing the compatibility mode to SQL Server 2050 (90) does not make any difference with regards to this error.I solved the problem by deleting the table dbo.sysdiagrams and letting SQL Server 2005 re-create it. Apparently, its schema was different.|||

????CONGRATULATIONS!!!!

And thank you very, very much. I had desesperated to resolve this problem with my diagram of forty three tables, that i think that i don′t save it, but you resolve my problem with a simple solution, the eternal "restart", or recreate the table in this case.

Thank you very much another time,

Zapa

Cannot create diagrams in Upgraded SQL Server 2000 Database

Dear all,

I am trying to save a newly created diagram in SQL Server 2005 SP1.

The error message is:
-Beginning of pasted error message

===================================

Cannot insert the value NULL into column 'diagram_id', table 'adt_db.dbo.sysdiagrams'; column does not allow nulls. INSERT fails.
The statement has been terminated.
The 'sp_creatediagram' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. (.Net SqlClient Data Provider)

Program Location:

at Microsoft.VisualStudio.DataTools.Interop.IDTDocTool.Save(Object dsRef, String path, Boolean okToOverwrite)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.DatabaseDesignerNode.Save(VSSAVEFLAGS dwSave, String strSilentSaveAsName, IVsUIShell pIVsUIShell, IntPtr punkDocDataIntPtr, String& strMkDocumentNew, Int32& pfCanceled)

-End of pasted error message

The database I use has been upgraded from SQL Server 2000.

I am running in SQL Server 2000 Compatibility Mode (80) but changing the compatibility mode to SQL Server 2050 (90) does not make any difference with regards to this error.I solved the problem by deleting the table dbo.sysdiagrams and letting SQL Server 2005 re-create it. Apparently, its schema was different.|||

????CONGRATULATIONS!!!!

And thank you very, very much. I had desesperated to resolve this problem with my diagram of forty three tables, that i think that i don′t save it, but you resolve my problem with a simple solution, the eternal "restart", or recreate the table in this case.

Thank you very much another time,

Zapa

Cannot create diagrams in SQLSERVER 2005

Hi,
Every time I click on the Database Diagram node in object explorer in SQL
Server Management Studio, I get a message:
Database diagram support objects cannot be installed because this database
does not have a valid owner. ...
I have checked the owner and it coincides with my logon name in my domain
(i.e. DENTDEVELOPMENT\JuanDent). What could be going on? Could I have a
problem with Active Directory? Why am I not being recognized as a valid db
owner?
Thanks in advance,
Juan Dent, M.Sc.
Make sure the compatibility level of the databases is set to
90 - that's often what causes the problem.
You can set it to 90 using:
EXEC sp_dbcmptlevel 'database name', '90'
-Sue
On Mon, 23 Jan 2006 17:04:01 -0800, Juan Dent
<Juan_Dent@.nospam.nospam> wrote:

>Hi,
>Every time I click on the Database Diagram node in object explorer in SQL
>Server Management Studio, I get a message:
> Database diagram support objects cannot be installed because this database
>does not have a valid owner. ...
>I have checked the owner and it coincides with my logon name in my domain
>(i.e. DENTDEVELOPMENT\JuanDent). What could be going on? Could I have a
>problem with Active Directory? Why am I not being recognized as a valid db
>owner?
|||Juan Dent (Juan_Dent@.nospam.nospam) writes:
> Every time I click on the Database Diagram node in object explorer in SQL
> Server Management Studio, I get a message:
> Database diagram support objects cannot be installed because this
> database does not have a valid owner. ...
> I have checked the owner and it coincides with my logon name in my domain
> (i.e. DENTDEVELOPMENT\JuanDent). What could be going on? Could I have a
> problem with Active Directory? Why am I not being recognized as a valid db
> owner?
This typically happens when you migrate a database from another server.
The problem can be seen by SELECT * FROM sys.database_principals. Compare
the row for dbo with a database created on the server.
I think changing the ownership to some other login, and back to yourself
fixes the issues.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
|||This site will help. There are two quick steps.
http://mcfunley.com/cs/blogs/dan/arc...12/23/899.aspx

************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Cannot create diagram in SQL 2005

i get the following message

Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects.

I am the db owner but still wouldnt let me install and create diagrams.

help!

cheers

I moved this thread from SSIS forum...I hope you can get better luck here...|||

hey i found the answer

you gotta set the owner to sa and then go to the database properties, then options, then change compatibility fromn sql 2000 (80) to sql 2005 (90)

too easy..

thanks buddy

Sunday, March 11, 2012

Cannot create diagram and not run jobs with my domain account logi

Hi!
I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
my domain account (HIK\Tommy) wich is a member of the Administrators group on
my computer and there is a corresponding Windows login account with sysadmin
permissions in SQL Server.
I can do most things with that account, BUT when I try to create a diagram
to a database. SQL does not like the owner of the database (my domain
account)
This is the error message that show up:
"Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or ALTER AUTHORIZATION statement to set the
database owner to a valid login, then add the database diagram support
objects."
Again when I try to run a job that is owned by my domain account (HIK\Tommy)
Following message arise:
"The job failed. Unable to determine if the owner (HIK\Tommy) of job
MaintenancePlan2 has server access (reason: Could not obtain information
about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
(Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
3621))."
I would be very grateful if you could come up with some suggestions.
Regards
TommyThis might be due to a mismatch between the 'dbo' user mapping and the
actual database owner. You can correct this with sp_changedbowner:
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> Hi!
> I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> my domain account (HIK\Tommy) wich is a member of the Administrators group
> on
> my computer and there is a corresponding Windows login account with
> sysadmin
> permissions in SQL Server.
> I can do most things with that account, BUT when I try to create a diagram
> to a database. SQL does not like the owner of the database (my domain
> account)
> This is the error message that show up:
> "Database diagram support objects cannot be installed because this
> database
> does not have a valid owner. To continue, first use the Files page of the
> Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> database owner to a valid login, then add the database diagram support
> objects."
> Again when I try to run a job that is owned by my domain account
> (HIK\Tommy)
> Following message arise:
> "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> MaintenancePlan2 has server access (reason: Could not obtain information
> about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> 3621))."
> I would be very grateful if you could come up with some suggestions.
> Regards
> Tommy|||Thanks for your suggestion but it does not work.
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
doesn't change anything.
On the other hand it 's possible to change user to sa and everything works
OK, so it's my domain name that is the trouble. Have never had this problem i
SQL Server 2K.
/Tommy
"Dan Guzman" wrote:
> This might be due to a mismatch between the 'dbo' user mapping and the
> actual database owner. You can correct this with sp_changedbowner:
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> > Hi!
> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> > my domain account (HIK\Tommy) wich is a member of the Administrators group
> > on
> > my computer and there is a corresponding Windows login account with
> > sysadmin
> > permissions in SQL Server.
> >
> > I can do most things with that account, BUT when I try to create a diagram
> > to a database. SQL does not like the owner of the database (my domain
> > account)
> >
> > This is the error message that show up:
> > "Database diagram support objects cannot be installed because this
> > database
> > does not have a valid owner. To continue, first use the Files page of the
> > Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> > database owner to a valid login, then add the database diagram support
> > objects."
> >
> > Again when I try to run a job that is owned by my domain account
> > (HIK\Tommy)
> >
> > Following message arise:
> >
> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> > MaintenancePlan2 has server access (reason: Could not obtain information
> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> > (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> > 3621))."
> >
> > I would be very grateful if you could come up with some suggestions.
> >
> > Regards
> > Tommy
>
>|||My apologies but I misread your post. I guess I should a finished my coffee
first :-)
For your first issue, the database needs to be in 90 compatibility mode in
order to create diagrams.
Regarding your second problem, run the SQL Server Configuration utility to
make sure the SQL Agent isn't running under the Network Service account.
Use a domain account.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> Thanks for your suggestion but it does not work.
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> doesn't change anything.
> On the other hand it 's possible to change user to sa and everything works
> OK, so it's my domain name that is the trouble. Have never had this
> problem i
> SQL Server 2K.
> /Tommy
> "Dan Guzman" wrote:
>> This might be due to a mismatch between the 'dbo' user mapping and the
>> actual database owner. You can correct this with sp_changedbowner:
>> USE MyDatabase
>> EXEC sp_changedbowner 'HIK\Tommy'
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> > Hi!
>> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
>> > with
>> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> > group
>> > on
>> > my computer and there is a corresponding Windows login account with
>> > sysadmin
>> > permissions in SQL Server.
>> >
>> > I can do most things with that account, BUT when I try to create a
>> > diagram
>> > to a database. SQL does not like the owner of the database (my domain
>> > account)
>> >
>> > This is the error message that show up:
>> > "Database diagram support objects cannot be installed because this
>> > database
>> > does not have a valid owner. To continue, first use the Files page of
>> > the
>> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
>> > the
>> > database owner to a valid login, then add the database diagram support
>> > objects."
>> >
>> > Again when I try to run a job that is owned by my domain account
>> > (HIK\Tommy)
>> >
>> > Following message arise:
>> >
>> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
>> > MaintenancePlan2 has server access (reason: Could not obtain
>> > information
>> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> > 42000]
>> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> > (Error
>> > 3621))."
>> >
>> > I would be very grateful if you could come up with some suggestions.
>> >
>> > Regards
>> > Tommy
>>|||Using a domain account for the Agent and SQL Server service solves the
problem with recognizeing job owner as my domain login (HIK\Tommy), but it
still don't like my domain login as database owner when trying to create a
diagram.
My administrator don't want me to use a domain account for services for
security reasons so, I'm going to use a workaround, e.g. use sa as owner
until this bug (?) is fixed.
Thank's anyway
Tommy
"Dan Guzman" wrote:
> My apologies but I misread your post. I guess I should a finished my coffee
> first :-)
> For your first issue, the database needs to be in 90 compatibility mode in
> order to create diagrams.
> Regarding your second problem, run the SQL Server Configuration utility to
> make sure the SQL Agent isn't running under the Network Service account.
> Use a domain account.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> > Thanks for your suggestion but it does not work.
> >
> > USE MyDatabase
> > EXEC sp_changedbowner 'HIK\Tommy'
> >
> > doesn't change anything.
> >
> > On the other hand it 's possible to change user to sa and everything works
> > OK, so it's my domain name that is the trouble. Have never had this
> > problem i
> > SQL Server 2K.
> >
> > /Tommy
> >
> > "Dan Guzman" wrote:
> >
> >> This might be due to a mismatch between the 'dbo' user mapping and the
> >> actual database owner. You can correct this with sp_changedbowner:
> >>
> >> USE MyDatabase
> >> EXEC sp_changedbowner 'HIK\Tommy'
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> >> > Hi!
> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
> >> > with
> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
> >> > group
> >> > on
> >> > my computer and there is a corresponding Windows login account with
> >> > sysadmin
> >> > permissions in SQL Server.
> >> >
> >> > I can do most things with that account, BUT when I try to create a
> >> > diagram
> >> > to a database. SQL does not like the owner of the database (my domain
> >> > account)
> >> >
> >> > This is the error message that show up:
> >> > "Database diagram support objects cannot be installed because this
> >> > database
> >> > does not have a valid owner. To continue, first use the Files page of
> >> > the
> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
> >> > the
> >> > database owner to a valid login, then add the database diagram support
> >> > objects."
> >> >
> >> > Again when I try to run a job that is owned by my domain account
> >> > (HIK\Tommy)
> >> >
> >> > Following message arise:
> >> >
> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> >> > MaintenancePlan2 has server access (reason: Could not obtain
> >> > information
> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
> >> > 42000]
> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
> >> > (Error
> >> > 3621))."
> >> >
> >> > I would be very grateful if you could come up with some suggestions.
> >> >
> >> > Regards
> >> > Tommy
> >>
> >>
> >>
>
>|||> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
The Books Online (Setting up Windows Accounts) states that it is best is to
use minimally privileged accounts for services. If you don't want to use a
low privilege domain user, you can use a (minimally privileged) local
Windows user account. I don't think this a a bug, it's just that SQL 2005
is more secure out-of-the-box so additional configuration work is needed to
loosen up security according to your organization's security policies.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:ED165CD9-5A84-4D4F-AC22-BF57C87A1A16@.microsoft.com...
> Using a domain account for the Agent and SQL Server service solves the
> problem with recognizeing job owner as my domain login (HIK\Tommy), but it
> still don't like my domain login as database owner when trying to create a
> diagram.
> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
> Thank's anyway
> Tommy
> "Dan Guzman" wrote:
>> My apologies but I misread your post. I guess I should a finished my
>> coffee
>> first :-)
>> For your first issue, the database needs to be in 90 compatibility mode
>> in
>> order to create diagrams.
>> Regarding your second problem, run the SQL Server Configuration utility
>> to
>> make sure the SQL Agent isn't running under the Network Service account.
>> Use a domain account.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
>> > Thanks for your suggestion but it does not work.
>> >
>> > USE MyDatabase
>> > EXEC sp_changedbowner 'HIK\Tommy'
>> >
>> > doesn't change anything.
>> >
>> > On the other hand it 's possible to change user to sa and everything
>> > works
>> > OK, so it's my domain name that is the trouble. Have never had this
>> > problem i
>> > SQL Server 2K.
>> >
>> > /Tommy
>> >
>> > "Dan Guzman" wrote:
>> >
>> >> This might be due to a mismatch between the 'dbo' user mapping and the
>> >> actual database owner. You can correct this with sp_changedbowner:
>> >>
>> >> USE MyDatabase
>> >> EXEC sp_changedbowner 'HIK\Tommy'
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Dan Guzman
>> >> SQL Server MVP
>> >>
>> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> >> > Hi!
>> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging
>> >> > in
>> >> > with
>> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> >> > group
>> >> > on
>> >> > my computer and there is a corresponding Windows login account with
>> >> > sysadmin
>> >> > permissions in SQL Server.
>> >> >
>> >> > I can do most things with that account, BUT when I try to create a
>> >> > diagram
>> >> > to a database. SQL does not like the owner of the database (my
>> >> > domain
>> >> > account)
>> >> >
>> >> > This is the error message that show up:
>> >> > "Database diagram support objects cannot be installed because this
>> >> > database
>> >> > does not have a valid owner. To continue, first use the Files page
>> >> > of
>> >> > the
>> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to
>> >> > set
>> >> > the
>> >> > database owner to a valid login, then add the database diagram
>> >> > support
>> >> > objects."
>> >> >
>> >> > Again when I try to run a job that is owned by my domain account
>> >> > (HIK\Tommy)
>> >> >
>> >> > Following message arise:
>> >> >
>> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of
>> >> > job
>> >> > MaintenancePlan2 has server access (reason: Could not obtain
>> >> > information
>> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> >> > 42000]
>> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> >> > (Error
>> >> > 3621))."
>> >> >
>> >> > I would be very grateful if you could come up with some suggestions.
>> >> >
>> >> > Regards
>> >> > Tommy
>> >>
>> >>
>> >>
>>

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Dear Bill

I am a newbie and have also experienced the same problem, on a local machine with SQL Server 2005 DE.

I have placed a similar msg on a few forums and no response to them as yet.

"MS SQL SERVER 2005 BUG? Cannot insert NULL into column diagram_id

Hi friends,

when trying to save a diagram I got an error:
The sp_creatediagram procedure attempted to return a status of NULL, which is not allowed."

Whats with this?

As far as I can work out, it has only started happening since I mucked around with the database properties such as ANSI NULLS true/false. I have put them back to default as a test and it doesnt fix the problem.

Have you got any ideas about it yet?

|||

This comes from the fact that the db was a prior version of sql server (via a conversion to 2005). This will not work.

You have to create the db brand new in sql server 2005, then import data from your sql server 2000 db, etc.

|||1. start>programs>microsoft visual studio 2005
2. file>new project>other project types>database>datbase project
3. connect to your database
4. solution explorer>database reference
5. server explorer>diagram
6. prompt: does not support diagram create?
7. click yes|||Bill - is this thread closed or do you still need help? If this is closed out you can mark it as "answered". Thanks!|||sounds good, but i had the same problem and this didn't work for me.|||

I have the same problem - is there any work around, or fix available?

I have tried to create the diagram from SQL Server Management Studio and Visual Studio 2005.

|||Are you trying to do this against SQL Server 2000 from 2005 or the other way around? Is the database set to a compatibility mode less than 9.0?|||

I have the same issue, and I have NEVER had SQL Server 2000 on any server here.

I am only getting this error on one or two of the 7 databases that I have on the SQL server instance.

--

Is there a way to delete the diagramming "stuff" so that when the create... option is chosen in Database Diagrams, it resets all of the sp's, etc.?

|||I'm not familiar with a way to do that. That isn't to say that there isn't one, so we'll leave this post open...Maybe someone will chime in!|||

Hi,

I had this problem as well (SQL 2005) - I simply deleted the sysdiagrams table from System Tables and created a new diagram allowing it to automatically create the database objects. This seemed to solve the problem.

Nick

|||

Hello:

This is what I did....

1. Created a Create Query for the System Tables > dbo.sysdiagrams

2. Changed the following statement:

[diagram_id] [int] DEFAULT ((0)),

3. Deleted the table: System Tables > dbo.sysdiagrams

4. Executed the modified query

5. Saved my diagram. It worked fine

6. I was even able to create and open multiple diagrams without any problems!

software786

|||Yes, this works. Ah, why isn't this fixed in SQL Server's updates?

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Dear Bill

I am a newbie and have also experienced the same problem, on a local machine with SQL Server 2005 DE.

I have placed a similar msg on a few forums and no response to them as yet.

"MS SQL SERVER 2005 BUG? Cannot insert NULL into column diagram_id

Hi friends,

when trying to save a diagram I got an error:
The sp_creatediagram procedure attempted to return a status of NULL, which is not allowed."

Whats with this?

As far as I can work out, it has only started happening since I mucked around with the database properties such as ANSI NULLS true/false. I have put them back to default as a test and it doesnt fix the problem.

Have you got any ideas about it yet?

|||

This comes from the fact that the db was a prior version of sql server (via a conversion to 2005). This will not work.

You have to create the db brand new in sql server 2005, then import data from your sql server 2000 db, etc.

|||1. start>programs>microsoft visual studio 2005
2. file>new project>other project types>database>datbase project
3. connect to your database
4. solution explorer>database reference
5. server explorer>diagram
6. prompt: does not support diagram create?
7. click yes|||Bill - is this thread closed or do you still need help? If this is closed out you can mark it as "answered". Thanks!|||sounds good, but i had the same problem and this didn't work for me.|||

I have the same problem - is there any work around, or fix available?

I have tried to create the diagram from SQL Server Management Studio and Visual Studio 2005.

|||Are you trying to do this against SQL Server 2000 from 2005 or the other way around? Is the database set to a compatibility mode less than 9.0?|||

I have the same issue, and I have NEVER had SQL Server 2000 on any server here.

I am only getting this error on one or two of the 7 databases that I have on the SQL server instance.

--

Is there a way to delete the diagramming "stuff" so that when the create... option is chosen in Database Diagrams, it resets all of the sp's, etc.?

|||I'm not familiar with a way to do that. That isn't to say that there isn't one, so we'll leave this post open...Maybe someone will chime in!|||

Hi,

I had this problem as well (SQL 2005) - I simply deleted the sysdiagrams table from System Tables and created a new diagram allowing it to automatically create the database objects. This seemed to solve the problem.

Nick

|||

Hello:

This is what I did....

1. Created a Create Query for the System Tables > dbo.sysdiagrams

2. Changed the following statement:

[diagram_id] [int] DEFAULT ((0)),

3. Deleted the table: System Tables > dbo.sysdiagrams

4. Executed the modified query

5. Saved my diagram. It worked fine

6. I was even able to create and open multiple diagrams without any problems!

software786

|||Yes, this works. Ah, why isn't this fixed in SQL Server's updates?

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Dear Bill

I am a newbie and have also experienced the same problem, on a local machine with SQL Server 2005 DE.

I have placed a similar msg on a few forums and no response to them as yet.

"MS SQL SERVER 2005 BUG? Cannot insert NULL into column diagram_id

Hi friends,

when trying to save a diagram I got an error:
The sp_creatediagram procedure attempted to return a status of NULL, which is not allowed."

Whats with this?

As far as I can work out, it has only started happening since I mucked around with the database properties such as ANSI NULLS true/false. I have put them back to default as a test and it doesnt fix the problem.

Have you got any ideas about it yet?

|||

This comes from the fact that the db was a prior version of sql server (via a conversion to 2005). This will not work.

You have to create the db brand new in sql server 2005, then import data from your sql server 2000 db, etc.

|||1. start>programs>microsoft visual studio 2005
2. file>new project>other project types>database>datbase project
3. connect to your database
4. solution explorer>database reference
5. server explorer>diagram
6. prompt: does not support diagram create?
7. click yes|||Bill - is this thread closed or do you still need help? If this is closed out you can mark it as "answered". Thanks!|||sounds good, but i had the same problem and this didn't work for me.|||

I have the same problem - is there any work around, or fix available?

I have tried to create the diagram from SQL Server Management Studio and Visual Studio 2005.

|||Are you trying to do this against SQL Server 2000 from 2005 or the other way around? Is the database set to a compatibility mode less than 9.0?|||

I have the same issue, and I have NEVER had SQL Server 2000 on any server here.

I am only getting this error on one or two of the 7 databases that I have on the SQL server instance.

--

Is there a way to delete the diagramming "stuff" so that when the create... option is chosen in Database Diagrams, it resets all of the sp's, etc.?

|||I'm not familiar with a way to do that. That isn't to say that there isn't one, so we'll leave this post open...Maybe someone will chime in!|||

Hi,

I had this problem as well (SQL 2005) - I simply deleted the sysdiagrams table from System Tables and created a new diagram allowing it to automatically create the database objects. This seemed to solve the problem.

Nick

|||

Hello:

This is what I did....

1. Created a Create Query for the System Tables > dbo.sysdiagrams

2. Changed the following statement:

[diagram_id] [int] DEFAULT ((0)),

3. Deleted the table: System Tables > dbo.sysdiagrams

4. Executed the modified query

5. Saved my diagram. It worked fine

6. I was even able to create and open multiple diagrams without any problems!

software786

|||Yes, this works. Ah, why isn't this fixed in SQL Server's updates?

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Dear Bill

I am a newbie and have also experienced the same problem, on a local machine with SQL Server 2005 DE.

I have placed a similar msg on a few forums and no response to them as yet.

"MS SQL SERVER 2005 BUG? Cannot insert NULL into column diagram_id

Hi friends,

when trying to save a diagram I got an error:
The sp_creatediagram procedure attempted to return a status of NULL, which is not allowed."

Whats with this?

As far as I can work out, it has only started happening since I mucked around with the database properties such as ANSI NULLS true/false. I have put them back to default as a test and it doesnt fix the problem.

Have you got any ideas about it yet?

|||

This comes from the fact that the db was a prior version of sql server (via a conversion to 2005). This will not work.

You have to create the db brand new in sql server 2005, then import data from your sql server 2000 db, etc.

|||1. start>programs>microsoft visual studio 2005
2. file>new project>other project types>database>datbase project
3. connect to your database
4. solution explorer>database reference
5. server explorer>diagram
6. prompt: does not support diagram create?
7. click yes|||Bill - is this thread closed or do you still need help? If this is closed out you can mark it as "answered". Thanks!|||sounds good, but i had the same problem and this didn't work for me.|||

I have the same problem - is there any work around, or fix available?

I have tried to create the diagram from SQL Server Management Studio and Visual Studio 2005.

|||Are you trying to do this against SQL Server 2000 from 2005 or the other way around? Is the database set to a compatibility mode less than 9.0?|||

I have the same issue, and I have NEVER had SQL Server 2000 on any server here.

I am only getting this error on one or two of the 7 databases that I have on the SQL server instance.

--

Is there a way to delete the diagramming "stuff" so that when the create... option is chosen in Database Diagrams, it resets all of the sp's, etc.?

|||I'm not familiar with a way to do that. That isn't to say that there isn't one, so we'll leave this post open...Maybe someone will chime in!|||

Hi,

I had this problem as well (SQL 2005) - I simply deleted the sysdiagrams table from System Tables and created a new diagram allowing it to automatically create the database objects. This seemed to solve the problem.

Nick

|||

Hello:

This is what I did....

1. Created a Create Query for the System Tables > dbo.sysdiagrams

2. Changed the following statement:

[diagram_id] [int] DEFAULT ((0)),

3. Deleted the table: System Tables > dbo.sysdiagrams

4. Executed the modified query

5. Saved my diagram. It worked fine

6. I was even able to create and open multiple diagrams without any problems!

software786

|||Yes, this works. Ah, why isn't this fixed in SQL Server's updates?

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Dear Bill

I am a newbie and have also experienced the same problem, on a local machine with SQL Server 2005 DE.

I have placed a similar msg on a few forums and no response to them as yet.

"MS SQL SERVER 2005 BUG? Cannot insert NULL into column diagram_id

Hi friends,

when trying to save a diagram I got an error:
The sp_creatediagram procedure attempted to return a status of NULL, which is not allowed."

Whats with this?

As far as I can work out, it has only started happening since I mucked around with the database properties such as ANSI NULLS true/false. I have put them back to default as a test and it doesnt fix the problem.

Have you got any ideas about it yet?

|||

This comes from the fact that the db was a prior version of sql server (via a conversion to 2005). This will not work.

You have to create the db brand new in sql server 2005, then import data from your sql server 2000 db, etc.

|||1. start>programs>microsoft visual studio 2005
2. file>new project>other project types>database>datbase project
3. connect to your database
4. solution explorer>database reference
5. server explorer>diagram
6. prompt: does not support diagram create?
7. click yes|||Bill - is this thread closed or do you still need help? If this is closed out you can mark it as "answered". Thanks!|||sounds good, but i had the same problem and this didn't work for me.|||

I have the same problem - is there any work around, or fix available?

I have tried to create the diagram from SQL Server Management Studio and Visual Studio 2005.

|||Are you trying to do this against SQL Server 2000 from 2005 or the other way around? Is the database set to a compatibility mode less than 9.0?|||

I have the same issue, and I have NEVER had SQL Server 2000 on any server here.

I am only getting this error on one or two of the 7 databases that I have on the SQL server instance.

--

Is there a way to delete the diagramming "stuff" so that when the create... option is chosen in Database Diagrams, it resets all of the sp's, etc.?

|||I'm not familiar with a way to do that. That isn't to say that there isn't one, so we'll leave this post open...Maybe someone will chime in!|||

Hi,

I had this problem as well (SQL 2005) - I simply deleted the sysdiagrams table from System Tables and created a new diagram allowing it to automatically create the database objects. This seemed to solve the problem.

Nick

|||

Hello:

This is what I did....

1. Created a Create Query for the System Tables > dbo.sysdiagrams

2. Changed the following statement:

[diagram_id] [int] DEFAULT ((0)),

3. Deleted the table: System Tables > dbo.sysdiagrams

4. Executed the modified query

5. Saved my diagram. It worked fine

6. I was even able to create and open multiple diagrams without any problems!

software786

|||Yes, this works. Ah, why isn't this fixed in SQL Server's updates?

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Did you encounter the same issue in all of the databases in the local SQL server? Or just particular database(s)? I guess the issue is caused by a database attached from previous SQL server (2000 or 7.0), if it does, please let me know.

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Dear Bill

I am a newbie and have also experienced the same problem, on a local machine with SQL Server 2005 DE.

I have placed a similar msg on a few forums and no response to them as yet.

"MS SQL SERVER 2005 BUG? Cannot insert NULL into column diagram_id

Hi friends,

when trying to save a diagram I got an error:
The sp_creatediagram procedure attempted to return a status of NULL, which is not allowed."

Whats with this?

As far as I can work out, it has only started happening since I mucked around with the database properties such as ANSI NULLS true/false. I have put them back to default as a test and it doesnt fix the problem.

Have you got any ideas about it yet?

|||

This comes from the fact that the db was a prior version of sql server (via a conversion to 2005). This will not work.

You have to create the db brand new in sql server 2005, then import data from your sql server 2000 db, etc.

|||1. start>programs>microsoft visual studio 2005
2. file>new project>other project types>database>datbase project
3. connect to your database
4. solution explorer>database reference
5. server explorer>diagram
6. prompt: does not support diagram create?
7. click yes|||Bill - is this thread closed or do you still need help? If this is closed out you can mark it as "answered". Thanks!|||sounds good, but i had the same problem and this didn't work for me.|||

I have the same problem - is there any work around, or fix available?

I have tried to create the diagram from SQL Server Management Studio and Visual Studio 2005.

|||Are you trying to do this against SQL Server 2000 from 2005 or the other way around? Is the database set to a compatibility mode less than 9.0?|||

I have the same issue, and I have NEVER had SQL Server 2000 on any server here.

I am only getting this error on one or two of the 7 databases that I have on the SQL server instance.

--

Is there a way to delete the diagramming "stuff" so that when the create... option is chosen in Database Diagrams, it resets all of the sp's, etc.?

|||I'm not familiar with a way to do that. That isn't to say that there isn't one, so we'll leave this post open...Maybe someone will chime in!|||

Hi,

I had this problem as well (SQL 2005) - I simply deleted the sysdiagrams table from System Tables and created a new diagram allowing it to automatically create the database objects. This seemed to solve the problem.

Nick

|||

Hello:

This is what I did....

1. Created a Create Query for the System Tables > dbo.sysdiagrams

2. Changed the following statement:

[diagram_id] [int] DEFAULT((0)),

3. Deleted the table: System Tables > dbo.sysdiagrams

4. Executed the modified query

5. Saved my diagram. It worked fine

6. I was even able to create and open multiple diagrams without any problems!

software786

|||Yes, this works. Ah, why isn't this fixed in SQL Server's updates?

Cannot create db diagram

When trying to create a DB diagram on my local SQL Server 2005 db, I get the following error:

cannot insert the value null into column "diagram_id"

I have searched the web and can't seem to find anything on this.

I just simply drag one table from my local db onto the diagram windows and try to Save it and that's what I get. I'm able to save diagrams on a networked SQL Server.

Does anybody know how I can resolve this issue?

Dear Bill

I am a newbie and have also experienced the same problem, on a local machine with SQL Server 2005 DE.

I have placed a similar msg on a few forums and no response to them as yet.

"MS SQL SERVER 2005 BUG? Cannot insert NULL into column diagram_id

Hi friends,

when trying to save a diagram I got an error:
The sp_creatediagram procedure attempted to return a status of NULL, which is not allowed."

Whats with this?

As far as I can work out, it has only started happening since I mucked around with the database properties such as ANSI NULLS true/false. I have put them back to default as a test and it doesnt fix the problem.

Have you got any ideas about it yet?

|||

This comes from the fact that the db was a prior version of sql server (via a conversion to 2005). This will not work.

You have to create the db brand new in sql server 2005, then import data from your sql server 2000 db, etc.

|||1. start>programs>microsoft visual studio 2005
2. file>new project>other project types>database>datbase project
3. connect to your database
4. solution explorer>database reference
5. server explorer>diagram
6. prompt: does not support diagram create?
7. click yes|||Bill - is this thread closed or do you still need help? If this is closed out you can mark it as "answered". Thanks!|||sounds good, but i had the same problem and this didn't work for me.|||

I have the same problem - is there any work around, or fix available?

I have tried to create the diagram from SQL Server Management Studio and Visual Studio 2005.

|||Are you trying to do this against SQL Server 2000 from 2005 or the other way around? Is the database set to a compatibility mode less than 9.0?|||

I have the same issue, and I have NEVER had SQL Server 2000 on any server here.

I am only getting this error on one or two of the 7 databases that I have on the SQL server instance.

--

Is there a way to delete the diagramming "stuff" so that when the create... option is chosen in Database Diagrams, it resets all of the sp's, etc.?

|||I'm not familiar with a way to do that. That isn't to say that there isn't one, so we'll leave this post open...Maybe someone will chime in!|||

Hi,

I had this problem as well (SQL 2005) - I simply deleted the sysdiagrams table from System Tables and created a new diagram allowing it to automatically create the database objects. This seemed to solve the problem.

Nick

|||

Hello:

This is what I did....

1. Created a Create Query for the System Tables > dbo.sysdiagrams

2. Changed the following statement:

[diagram_id] [int] DEFAULT ((0)),

3. Deleted the table: System Tables > dbo.sysdiagrams

4. Executed the modified query

5. Saved my diagram. It worked fine

6. I was even able to create and open multiple diagrams without any problems!

software786

|||Yes, this works. Ah, why isn't this fixed in SQL Server's updates?