After attaching Sql Server 7 database can't make a diagram

I have successfully attached an sql server 7 database, changed the owner to
sa and the compatibility level to 2000 but when I try to create a diagram, I
get the following message. I go to the MS site and it is no help:
TITLE: Microsoft SQL Server Management Studio
--
Invalid column name 'uvalue'.
Invalid column name 'uvalue'.
Could not find stored procedure 'dbo.sp_upgraddiagrams'.
Object is invalid. Extended properties are not permitted on
'dbo.sysdiagrams', or the object does not exist.
Object is invalid. Extended properties are not permitted on
'dbo.sp_upgraddiagrams', or the object does not exist. (Microsoft SQL
Server, Error: 207)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
--
BUTTONS:
OKHi Ellie
The link talks about case sensitive collations. What collation are you using?
It also mentions Management Studio, but you said SQL 2000!
John
"Ellie" wrote:
> I have successfully attached an sql server 7 database, changed the owner to
> sa and the compatibility level to 2000 but when I try to create a diagram, I
> get the following message. I go to the MS site and it is no help:
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Invalid column name 'uvalue'.
> Invalid column name 'uvalue'.
> Could not find stored procedure 'dbo.sp_upgraddiagrams'.
> Object is invalid. Extended properties are not permitted on
> 'dbo.sysdiagrams', or the object does not exist.
> Object is invalid. Extended properties are not permitted on
> 'dbo.sp_upgraddiagrams', or the object does not exist. (Microsoft SQL
> Server, Error: 207)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
> --
> BUTTONS:
> OK
>
>|||Hi John,
The collation is:
SQL_Latin1_General_CP1_CI_AS
It was the default. I am using Sql Server 2005 but made the database
compatible with 2000. I'm really not that familiar with the workings of the
server. I have another database that I am able to use the diagrams and it
looks like I have the same settings as this one so I don't know what's
wrong. Thanks Ellie
-- Original Message --
From: "John Bell" <jbellnewsposts@.hotmail.com>
Newsgroups: microsoft.public.sqlserver.server
Sent: Wednesday, January 23, 2008 3:33 AM
Subject: RE: After attaching Sql Server 7 database can't make a diagram
> Hi Ellie
> The link talks about case sensitive collations. What collation are you
> using?
> It also mentions Management Studio, but you said SQL 2000!
> John
> "Ellie" wrote:
>> I have successfully attached an sql server 7 database, changed the owner
>> to
>> sa and the compatibility level to 2000 but when I try to create a
>> diagram, I
>> get the following message. I go to the MS site and it is no help:
>>
>> TITLE: Microsoft SQL Server Management Studio
>> --
>> Invalid column name 'uvalue'.
>> Invalid column name 'uvalue'.
>> Could not find stored procedure 'dbo.sp_upgraddiagrams'.
>> Object is invalid. Extended properties are not permitted on
>> 'dbo.sysdiagrams', or the object does not exist.
>> Object is invalid. Extended properties are not permitted on
>> 'dbo.sp_upgraddiagrams', or the object does not exist. (Microsoft SQL
>> Server, Error: 207)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
>> --
>> BUTTONS:
>> OK
>>
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:3EF7E80C-B854-4EF9-B1CF-D0B2F345E544@.microsoft.com...
> Hi Ellie
> The link talks about case sensitive collations. What collation are you
> using?
> It also mentions Management Studio, but you said SQL 2000!
> John
> "Ellie" wrote:
>> I have successfully attached an sql server 7 database, changed the owner
>> to
>> sa and the compatibility level to 2000 but when I try to create a
>> diagram, I
>> get the following message. I go to the MS site and it is no help:
>>
>> TITLE: Microsoft SQL Server Management Studio
>> --
>> Invalid column name 'uvalue'.
>> Invalid column name 'uvalue'.
>> Could not find stored procedure 'dbo.sp_upgraddiagrams'.
>> Object is invalid. Extended properties are not permitted on
>> 'dbo.sysdiagrams', or the object does not exist.
>> Object is invalid. Extended properties are not permitted on
>> 'dbo.sp_upgraddiagrams', or the object does not exist. (Microsoft SQL
>> Server, Error: 207)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
>> --
>> BUTTONS:
>> OK
>>|||Hi Ellie
I can't say I use diagrams much! The easiest option may be to drop them
before detaching and re-creating them when they on the destination system.
Which @.@.version of SQL 2005 are you using?
John
"Ellie" wrote:
> Hi John,
> The collation is:
> SQL_Latin1_General_CP1_CI_AS
> It was the default. I am using Sql Server 2005 but made the database
> compatible with 2000. I'm really not that familiar with the workings of the
> server. I have another database that I am able to use the diagrams and it
> looks like I have the same settings as this one so I don't know what's
> wrong. Thanks Ellie
> -- Original Message --
> From: "John Bell" <jbellnewsposts@.hotmail.com>
> Newsgroups: microsoft.public.sqlserver.server
> Sent: Wednesday, January 23, 2008 3:33 AM
> Subject: RE: After attaching Sql Server 7 database can't make a diagram
>
> > Hi Ellie
> >
> > The link talks about case sensitive collations. What collation are you
> > using?
> >
> > It also mentions Management Studio, but you said SQL 2000!
> >
> > John
> >
> > "Ellie" wrote:
> >
> >>
> >> I have successfully attached an sql server 7 database, changed the owner
> >> to
> >> sa and the compatibility level to 2000 but when I try to create a
> >> diagram, I
> >> get the following message. I go to the MS site and it is no help:
> >>
> >>
> >> TITLE: Microsoft SQL Server Management Studio
> >> --
> >>
> >> Invalid column name 'uvalue'.
> >> Invalid column name 'uvalue'.
> >> Could not find stored procedure 'dbo.sp_upgraddiagrams'.
> >> Object is invalid. Extended properties are not permitted on
> >> 'dbo.sysdiagrams', or the object does not exist.
> >> Object is invalid. Extended properties are not permitted on
> >> 'dbo.sp_upgraddiagrams', or the object does not exist. (Microsoft SQL
> >> Server, Error: 207)
> >>
> >> For help, click:
> >> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
> >>
> >> --
> >> BUTTONS:
> >>
> >> OK
> >>
> >>
> >>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3EF7E80C-B854-4EF9-B1CF-D0B2F345E544@.microsoft.com...
> > Hi Ellie
> >
> > The link talks about case sensitive collations. What collation are you
> > using?
> >
> > It also mentions Management Studio, but you said SQL 2000!
> >
> > John
> >
> > "Ellie" wrote:
> >
> >>
> >> I have successfully attached an sql server 7 database, changed the owner
> >> to
> >> sa and the compatibility level to 2000 but when I try to create a
> >> diagram, I
> >> get the following message. I go to the MS site and it is no help:
> >>
> >>
> >> TITLE: Microsoft SQL Server Management Studio
> >> --
> >>
> >> Invalid column name 'uvalue'.
> >> Invalid column name 'uvalue'.
> >> Could not find stored procedure 'dbo.sp_upgraddiagrams'.
> >> Object is invalid. Extended properties are not permitted on
> >> 'dbo.sysdiagrams', or the object does not exist.
> >> Object is invalid. Extended properties are not permitted on
> >> 'dbo.sp_upgraddiagrams', or the object does not exist. (Microsoft SQL
> >> Server, Error: 207)
> >>
> >> For help, click:
> >> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=207&LinkId=20476
> >>
> >> --
> >> BUTTONS:
> >>
> >> OK
> >>
> >>
> >>
>
>