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
> >>
> >>
> >>
>
>
Showing posts with label attached. Show all posts
Showing posts with label attached. Show all posts
Sunday, February 12, 2012
After attaching database it is in Read only mode
Hi,
I detached a database from Server1 and took MDF file to Server2.
After that I re-attached the database on Server1.
When I tried to attached database using EM, sp_attach_db and also
sp_Attach_single_file, i was getting error msg 1813.
So I detached database again from Server1 and used the LDF on Server2.
It recognizes and LDF file and attaches the database. However, the
database is in read-only mode. I can go to properties and uncheck
"Read-Only" but when I try to save the changes it gives me Error 5105
- Deactivation Error...
I don't have access to new MDF file after I detached it again.
Any help will be greatly appreciated.
Divyesh
Check the file properties for the mdf and ldf at the
operating system level and make sure the files themselves
are not set to read only for the file properties.
-Sue
On 1 Dec 2004 13:53:26 -0800, divyeshkhatri@.hotmail.com
(Divyesh) wrote:
>Hi,
>I detached a database from Server1 and took MDF file to Server2.
>After that I re-attached the database on Server1.
>When I tried to attached database using EM, sp_attach_db and also
>sp_Attach_single_file, i was getting error msg 1813.
>So I detached database again from Server1 and used the LDF on Server2.
> It recognizes and LDF file and attaches the database. However, the
>database is in read-only mode. I can go to properties and uncheck
>"Read-Only" but when I try to save the changes it gives me Error 5105
>- Deactivation Error...
>I don't have access to new MDF file after I detached it again.
>Any help will be greatly appreciated.
>Divyesh
I detached a database from Server1 and took MDF file to Server2.
After that I re-attached the database on Server1.
When I tried to attached database using EM, sp_attach_db and also
sp_Attach_single_file, i was getting error msg 1813.
So I detached database again from Server1 and used the LDF on Server2.
It recognizes and LDF file and attaches the database. However, the
database is in read-only mode. I can go to properties and uncheck
"Read-Only" but when I try to save the changes it gives me Error 5105
- Deactivation Error...
I don't have access to new MDF file after I detached it again.
Any help will be greatly appreciated.
Divyesh
Check the file properties for the mdf and ldf at the
operating system level and make sure the files themselves
are not set to read only for the file properties.
-Sue
On 1 Dec 2004 13:53:26 -0800, divyeshkhatri@.hotmail.com
(Divyesh) wrote:
>Hi,
>I detached a database from Server1 and took MDF file to Server2.
>After that I re-attached the database on Server1.
>When I tried to attached database using EM, sp_attach_db and also
>sp_Attach_single_file, i was getting error msg 1813.
>So I detached database again from Server1 and used the LDF on Server2.
> It recognizes and LDF file and attaches the database. However, the
>database is in read-only mode. I can go to properties and uncheck
>"Read-Only" but when I try to save the changes it gives me Error 5105
>- Deactivation Error...
>I don't have access to new MDF file after I detached it again.
>Any help will be greatly appreciated.
>Divyesh
After attaching database it is in Read only mode
Hi,
I detached a database from Server1 and took MDF file to Server2.
After that I re-attached the database on Server1.
When I tried to attached database using EM, sp_attach_db and also
sp_Attach_single_file, i was getting error msg 1813.
So I detached database again from Server1 and used the LDF on Server2.
It recognizes and LDF file and attaches the database. However, the
database is in read-only mode. I can go to properties and uncheck
"Read-Only" but when I try to save the changes it gives me Error 5105
- Deactivation Error...
I don't have access to new MDF file after I detached it again.
Any help will be greatly appreciated.
DivyeshCheck the file properties for the mdf and ldf at the
operating system level and make sure the files themselves
are not set to read only for the file properties.
-Sue
On 1 Dec 2004 13:53:26 -0800, divyeshkhatri@.hotmail.com
(Divyesh) wrote:
>Hi,
>I detached a database from Server1 and took MDF file to Server2.
>After that I re-attached the database on Server1.
>When I tried to attached database using EM, sp_attach_db and also
>sp_Attach_single_file, i was getting error msg 1813.
>So I detached database again from Server1 and used the LDF on Server2.
> It recognizes and LDF file and attaches the database. However, the
>database is in read-only mode. I can go to properties and uncheck
>"Read-Only" but when I try to save the changes it gives me Error 5105
>- Deactivation Error...
>I don't have access to new MDF file after I detached it again.
>Any help will be greatly appreciated.
>Divyesh
I detached a database from Server1 and took MDF file to Server2.
After that I re-attached the database on Server1.
When I tried to attached database using EM, sp_attach_db and also
sp_Attach_single_file, i was getting error msg 1813.
So I detached database again from Server1 and used the LDF on Server2.
It recognizes and LDF file and attaches the database. However, the
database is in read-only mode. I can go to properties and uncheck
"Read-Only" but when I try to save the changes it gives me Error 5105
- Deactivation Error...
I don't have access to new MDF file after I detached it again.
Any help will be greatly appreciated.
DivyeshCheck the file properties for the mdf and ldf at the
operating system level and make sure the files themselves
are not set to read only for the file properties.
-Sue
On 1 Dec 2004 13:53:26 -0800, divyeshkhatri@.hotmail.com
(Divyesh) wrote:
>Hi,
>I detached a database from Server1 and took MDF file to Server2.
>After that I re-attached the database on Server1.
>When I tried to attached database using EM, sp_attach_db and also
>sp_Attach_single_file, i was getting error msg 1813.
>So I detached database again from Server1 and used the LDF on Server2.
> It recognizes and LDF file and attaches the database. However, the
>database is in read-only mode. I can go to properties and uncheck
>"Read-Only" but when I try to save the changes it gives me Error 5105
>- Deactivation Error...
>I don't have access to new MDF file after I detached it again.
>Any help will be greatly appreciated.
>Divyesh
After attaching database it is in Read only mode
Hi,
I detached a database from Server1 and took MDF file to Server2.
After that I re-attached the database on Server1.
When I tried to attached database using EM, sp_attach_db and also
sp_Attach_single_file, i was getting error msg 1813.
So I detached database again from Server1 and used the LDF on Server2.
It recognizes and LDF file and attaches the database. However, the
database is in read-only mode. I can go to properties and uncheck
"Read-Only" but when I try to save the changes it gives me Error 5105
- Deactivation Error...
I don't have access to new MDF file after I detached it again.
Any help will be greatly appreciated.
DivyeshCheck the file properties for the mdf and ldf at the
operating system level and make sure the files themselves
are not set to read only for the file properties.
-Sue
On 1 Dec 2004 13:53:26 -0800, divyeshkhatri@.hotmail.com
(Divyesh) wrote:
>Hi,
>I detached a database from Server1 and took MDF file to Server2.
>After that I re-attached the database on Server1.
>When I tried to attached database using EM, sp_attach_db and also
>sp_Attach_single_file, i was getting error msg 1813.
>So I detached database again from Server1 and used the LDF on Server2.
> It recognizes and LDF file and attaches the database. However, the
>database is in read-only mode. I can go to properties and uncheck
>"Read-Only" but when I try to save the changes it gives me Error 5105
>- Deactivation Error...
>I don't have access to new MDF file after I detached it again.
>Any help will be greatly appreciated.
>Divyesh
I detached a database from Server1 and took MDF file to Server2.
After that I re-attached the database on Server1.
When I tried to attached database using EM, sp_attach_db and also
sp_Attach_single_file, i was getting error msg 1813.
So I detached database again from Server1 and used the LDF on Server2.
It recognizes and LDF file and attaches the database. However, the
database is in read-only mode. I can go to properties and uncheck
"Read-Only" but when I try to save the changes it gives me Error 5105
- Deactivation Error...
I don't have access to new MDF file after I detached it again.
Any help will be greatly appreciated.
DivyeshCheck the file properties for the mdf and ldf at the
operating system level and make sure the files themselves
are not set to read only for the file properties.
-Sue
On 1 Dec 2004 13:53:26 -0800, divyeshkhatri@.hotmail.com
(Divyesh) wrote:
>Hi,
>I detached a database from Server1 and took MDF file to Server2.
>After that I re-attached the database on Server1.
>When I tried to attached database using EM, sp_attach_db and also
>sp_Attach_single_file, i was getting error msg 1813.
>So I detached database again from Server1 and used the LDF on Server2.
> It recognizes and LDF file and attaches the database. However, the
>database is in read-only mode. I can go to properties and uncheck
>"Read-Only" but when I try to save the changes it gives me Error 5105
>- Deactivation Error...
>I don't have access to new MDF file after I detached it again.
>Any help will be greatly appreciated.
>Divyesh
Subscribe to:
Posts (Atom)