Showing posts with label attach. Show all posts
Showing posts with label attach. Show all posts

Sunday, March 25, 2012

Case Sensitive Flag

I have a customer with MS-SQL7 they have to have the case sensitive flag on
for a database they purchased some time ago. Can I attach a database to the
same SQL server and some how remove the case sensitive flag for just this DB
?Not possible - this is set at the server level and affects all databases.
"Dan C" <anonymous@.discussions.microsoft.com> wrote in message
news:8D10190E-A01E-4950-B2AE-F62BCBD2C6A9@.microsoft.com...
quote:

> I have a customer with MS-SQL7 they have to have the case sensitive flag

on for a database they purchased some time ago. Can I attach a database to
the same SQL server and some how remove the case sensitive flag for just
this DB?|||Hi Dan,
You (or your customer) is out of luck there. The collation (which includes
among other things the setting for case sensitivity) is a server wide
setting on SQL Server 7. You either need a separate server for that
database, or you need to upgrade to SQL Server 2000, or you can install a
named instance of SQL Server 2000 (with the appropriate collation) on the
same machine as SQL Server 7 is running on.
Jacco Schalkwijk
SQL Server MVP
"Dan C" <anonymous@.discussions.microsoft.com> wrote in message
news:8D10190E-A01E-4950-B2AE-F62BCBD2C6A9@.microsoft.com...
quote:

> I have a customer with MS-SQL7 they have to have the case sensitive flag

on for a database they purchased some time ago. Can I attach a database to
the same SQL server and some how remove the case sensitive flag for just
this DB?

Case Sensitive Flag

I have a customer with MS-SQL7 they have to have the case sensitive flag on for a database they purchased some time ago. Can I attach a database to the same SQL server and some how remove the case sensitive flag for just this DB?Not possible - this is set at the server level and affects all databases.
"Dan C" <anonymous@.discussions.microsoft.com> wrote in message
news:8D10190E-A01E-4950-B2AE-F62BCBD2C6A9@.microsoft.com...
> I have a customer with MS-SQL7 they have to have the case sensitive flag
on for a database they purchased some time ago. Can I attach a database to
the same SQL server and some how remove the case sensitive flag for just
this DB?|||Hi Dan,
You (or your customer) is out of luck there. The collation (which includes
among other things the setting for case sensitivity) is a server wide
setting on SQL Server 7. You either need a separate server for that
database, or you need to upgrade to SQL Server 2000, or you can install a
named instance of SQL Server 2000 (with the appropriate collation) on the
same machine as SQL Server 7 is running on.
--
Jacco Schalkwijk
SQL Server MVP
"Dan C" <anonymous@.discussions.microsoft.com> wrote in message
news:8D10190E-A01E-4950-B2AE-F62BCBD2C6A9@.microsoft.com...
> I have a customer with MS-SQL7 they have to have the case sensitive flag
on for a database they purchased some time ago. Can I attach a database to
the same SQL server and some how remove the case sensitive flag for just
this DB?sql

Thursday, March 22, 2012

Case Sensative Coallation

I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I attach, it remains case sensative. How can I change it to insensative?I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the database changes case sensitivity?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?|||The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case sensative database to an instance of SQL server which was originally installed with Collation Settings insensative, and have the database act accordingly.
"Tibor Karaszi" wrote:
> I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the database changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> > I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
> attach, it remains case sensative. How can I change it to insensative?
>
>|||I see. Sorry to say that, but collation goes with the database. Changing collation is not an easy task, search
the archives for more info. If you don't find info there, you can post again...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case
sensative database to an instance of SQL server which was originally installed with Collation Settings
insensative, and have the database act accordingly.
> "Tibor Karaszi" wrote:
> > I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case
sensitivity
> > follows with the database. Can you point to how you determine that the database changes case sensitivity?
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> > news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> > > I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but
when I
> > attach, it remains case sensative. How can I change it to insensative?
> >
> >
> >

Case Sensative Coallation

I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I attach, it remains case sensative. How can I change it to insensative?
I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the database changes case sensitivity?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?
|||The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case sensative database to an instance of SQL server which was originally installed with Collation Settings insensative, and have the database act accordi
ngly.
"Tibor Karaszi" wrote:

> I assume that you mean that you want to attach a SQL Server *database*, not an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the database changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> attach, it remains case sensative. How can I change it to insensative?
>
>
|||I see. Sorry to say that, but collation goes with the database. Changing collation is not an easy task, search
the archives for more info. If you don't find info there, you can post again...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping that I could attach a case
sensative database to an instance of SQL server which was originally installed with Collation Settings
insensative, and have the database act accordingly.[vbcol=seagreen]
> "Tibor Karaszi" wrote:
sensitivity[vbcol=seagreen]
when I[vbcol=seagreen]

Case Sensative Coallation

I have a case-sensative database which I want to attach to an insensative in
stance of SQL Server, but when I attach, it remains case sensative. How can
I change it to insensative?I assume that you mean that you want to attach a SQL Server *database*, not
an *instance*. Case sensitivity
follows with the database. Can you point to how you determine that the datab
ase changes case sensitivity?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> I have a case-sensative database which I want to attach to an insensative instance
of SQL Server, but when I
attach, it remains case sensative. How can I change it to insensative?|||The database doesn't change sensativity. Sorry for any confusion. I was hopi
ng that I could attach a case sensative database to an instance of SQL serve
r which was originally installed with Collation Settings insensative, and ha
ve the database act accordi
ngly.
"Tibor Karaszi" wrote:

> I assume that you mean that you want to attach a SQL Server *database*, no
t an *instance*. Case sensitivity
> follows with the database. Can you point to how you determine that the dat
abase changes case sensitivity?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
> news:FEA9C167-4E33-4E73-88F0-6BD32287C578@.microsoft.com...
> attach, it remains case sensative. How can I change it to insensative?
>
>|||I see. Sorry to say that, but collation goes with the database. Changing col
lation is not an easy task, search
the archives for more info. If you don't find info there, you can post again
..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"JDArsenault" <JDArsenault@.discussions.microsoft.com> wrote in message
news:55CCFB46-5F43-46A0-B53D-CE7C443AA30C@.microsoft.com...
> The database doesn't change sensativity. Sorry for any confusion. I was hoping tha
t I could attach a case
sensative database to an instance of SQL server which was originally install
ed with Collation Settings
insensative, and have the database act accordingly.[vbcol=seagreen]
> "Tibor Karaszi" wrote:
>
sensitivity[vbcol=seagreen]
when I[vbcol=seagreen]sql

Wednesday, March 7, 2012

carry database of 2000 to new computer with SQL Server 2005

I used "detach" in old computer with running SQL SERVER 2000 and copy the
A.MDF file to the new computer with SQL Server 2005.
Then used "attach" to restore the database A in the new computer. The
database A still keeps the user names and machine name. I can not delete them.
The problem is that I can not expand the folder of Database Diagrams. When I
do it, I got the 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
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 did the "use the Files page of Database Properties dialog box to to set
the database owner to a valid login", by using a new computer valid user
name. But it does not work. I do not know how "then add the database diagram
support objects" either.
Thanks for any help.
Dabin>I used "detach" in old computer with running SQL SERVER 2000 and copy the
> A.MDF file to the new computer with SQL Server 2005.
OK, should be fine.
> Then used "attach" to restore the database A in the new computer. The
> database A still keeps the user names and machine name. I can not delete them.
User names are expected. Yes, you can remove these if you wish. Check out DROP USER.
SQL Server does not store the machine name inside the database, except for the master and msdb
databases.
> The problem is that I can not expand the folder of Database Diagrams. When I
> do it, I got the 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
> 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.
You need to set the owner to a login that exists as a login inside SQL Server. After that is done
(and restart SSMS just in case), SSMS will add the procedures etc automatically.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"david" <david@.discussions.microsoft.com> wrote in message
news:4838E101-064B-4658-8F73-85696E7FB195@.microsoft.com...
>I used "detach" in old computer with running SQL SERVER 2000 and copy the
> A.MDF file to the new computer with SQL Server 2005.
> Then used "attach" to restore the database A in the new computer. The
> database A still keeps the user names and machine name. I can not delete them.
> The problem is that I can not expand the folder of Database Diagrams. When I
> do it, I got the 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
> 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 did the "use the Files page of Database Properties dialog box to to set
> the database owner to a valid login", by using a new computer valid user
> name. But it does not work. I do not know how "then add the database diagram
> support objects" either.
> Thanks for any help.
> Dabin|||Thank you, Tibor:
My problem is the last one "You need to set the owner to a login that exists
as a login inside SQL Server. After that is done
(and restart SSMS just in case), SSMS will add the procedures etc
automatically.
--
"
I did something wrong.
I login to computer system, computer, by using my account, for example,
david. So the full name: computer\david.
I used SSMS to connect the database dbase. I right click on the database and
select the Properties. In the popup window, select Files. In the owner bos,
browser my account name, computer\david. Then click OK.
Restart SSMS. Tried to open the database diagrams, and I got the same error
massage.
David
"Tibor Karaszi" wrote:
> >I used "detach" in old computer with running SQL SERVER 2000 and copy the
> > A.MDF file to the new computer with SQL Server 2005.
> OK, should be fine.
>
> > Then used "attach" to restore the database A in the new computer. The
> > database A still keeps the user names and machine name. I can not delete them.
> User names are expected. Yes, you can remove these if you wish. Check out DROP USER.
> SQL Server does not store the machine name inside the database, except for the master and msdb
> databases.
>
> > The problem is that I can not expand the folder of Database Diagrams. When I
> > do it, I got the 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
> > 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.
> You need to set the owner to a login that exists as a login inside SQL Server. After that is done
> (and restart SSMS just in case), SSMS will add the procedures etc automatically.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "david" <david@.discussions.microsoft.com> wrote in message
> news:4838E101-064B-4658-8F73-85696E7FB195@.microsoft.com...
> >I used "detach" in old computer with running SQL SERVER 2000 and copy the
> > A.MDF file to the new computer with SQL Server 2005.
> > Then used "attach" to restore the database A in the new computer. The
> > database A still keeps the user names and machine name. I can not delete them.
> >
> > The problem is that I can not expand the folder of Database Diagrams. When I
> > do it, I got the 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
> > 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 did the "use the Files page of Database Properties dialog box to to set
> > the database owner to a valid login", by using a new computer valid user
> > name. But it does not work. I do not know how "then add the database diagram
> > support objects" either.
> >
> > Thanks for any help.
> >
> > Dabin
>|||IT seems you did set the owner to a valid login. You could try to set the owner to "sa" and see if
that helps. If not, I'm out of ideas, I'm afraid.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"david" <david@.discussions.microsoft.com> wrote in message
news:7F6BE323-F22F-42E1-846F-3CB685913381@.microsoft.com...
> Thank you, Tibor:
> My problem is the last one "You need to set the owner to a login that exists
> as a login inside SQL Server. After that is done
> (and restart SSMS just in case), SSMS will add the procedures etc
> automatically.
> --
> "
> I did something wrong.
> I login to computer system, computer, by using my account, for example,
> david. So the full name: computer\david.
> I used SSMS to connect the database dbase. I right click on the database and
> select the Properties. In the popup window, select Files. In the owner bos,
> browser my account name, computer\david. Then click OK.
> Restart SSMS. Tried to open the database diagrams, and I got the same error
> massage.
> David
> "Tibor Karaszi" wrote:
>> >I used "detach" in old computer with running SQL SERVER 2000 and copy the
>> > A.MDF file to the new computer with SQL Server 2005.
>> OK, should be fine.
>>
>> > Then used "attach" to restore the database A in the new computer. The
>> > database A still keeps the user names and machine name. I can not delete them.
>> User names are expected. Yes, you can remove these if you wish. Check out DROP USER.
>> SQL Server does not store the machine name inside the database, except for the master and msdb
>> databases.
>>
>> > The problem is that I can not expand the folder of Database Diagrams. When I
>> > do it, I got the 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
>> > 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.
>> You need to set the owner to a login that exists as a login inside SQL Server. After that is done
>> (and restart SSMS just in case), SSMS will add the procedures etc automatically.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "david" <david@.discussions.microsoft.com> wrote in message
>> news:4838E101-064B-4658-8F73-85696E7FB195@.microsoft.com...
>> >I used "detach" in old computer with running SQL SERVER 2000 and copy the
>> > A.MDF file to the new computer with SQL Server 2005.
>> > Then used "attach" to restore the database A in the new computer. The
>> > database A still keeps the user names and machine name. I can not delete them.
>> >
>> > The problem is that I can not expand the folder of Database Diagrams. When I
>> > do it, I got the 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
>> > 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 did the "use the Files page of Database Properties dialog box to to set
>> > the database owner to a valid login", by using a new computer valid user
>> > name. But it does not work. I do not know how "then add the database diagram
>> > support objects" either.
>> >
>> > Thanks for any help.
>> >
>> > Dabin|||Hi David,
I got the same error and fixed it by
right click on database
properties
files
options
Then change the compatibility from 80 which is SQL2000 to 90 which is
SQL2005.
"Tibor Karaszi" wrote:
> IT seems you did set the owner to a valid login. You could try to set the owner to "sa" and see if
> that helps. If not, I'm out of ideas, I'm afraid.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "david" <david@.discussions.microsoft.com> wrote in message
> news:7F6BE323-F22F-42E1-846F-3CB685913381@.microsoft.com...
> > Thank you, Tibor:
> > My problem is the last one "You need to set the owner to a login that exists
> > as a login inside SQL Server. After that is done
> > (and restart SSMS just in case), SSMS will add the procedures etc
> > automatically.
> > --
> > "
> >
> > I did something wrong.
> > I login to computer system, computer, by using my account, for example,
> > david. So the full name: computer\david.
> > I used SSMS to connect the database dbase. I right click on the database and
> > select the Properties. In the popup window, select Files. In the owner bos,
> > browser my account name, computer\david. Then click OK.
> > Restart SSMS. Tried to open the database diagrams, and I got the same error
> > massage.
> >
> > David
> >
> > "Tibor Karaszi" wrote:
> >
> >> >I used "detach" in old computer with running SQL SERVER 2000 and copy the
> >> > A.MDF file to the new computer with SQL Server 2005.
> >>
> >> OK, should be fine.
> >>
> >>
> >> > Then used "attach" to restore the database A in the new computer. The
> >> > database A still keeps the user names and machine name. I can not delete them.
> >>
> >> User names are expected. Yes, you can remove these if you wish. Check out DROP USER.
> >> SQL Server does not store the machine name inside the database, except for the master and msdb
> >> databases.
> >>
> >>
> >> > The problem is that I can not expand the folder of Database Diagrams. When I
> >> > do it, I got the 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
> >> > 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.
> >>
> >> You need to set the owner to a login that exists as a login inside SQL Server. After that is done
> >> (and restart SSMS just in case), SSMS will add the procedures etc automatically.
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "david" <david@.discussions.microsoft.com> wrote in message
> >> news:4838E101-064B-4658-8F73-85696E7FB195@.microsoft.com...
> >> >I used "detach" in old computer with running SQL SERVER 2000 and copy the
> >> > A.MDF file to the new computer with SQL Server 2005.
> >> > Then used "attach" to restore the database A in the new computer. The
> >> > database A still keeps the user names and machine name. I can not delete them.
> >> >
> >> > The problem is that I can not expand the folder of Database Diagrams. When I
> >> > do it, I got the 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
> >> > 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 did the "use the Files page of Database Properties dialog box to to set
> >> > the database owner to a valid login", by using a new computer valid user
> >> > name. But it does not work. I do not know how "then add the database diagram
> >> > support objects" either.
> >> >
> >> > Thanks for any help.
> >> >
> >> > Dabin
> >>
>

carry database of 2000 to new computer with SQL Server 2005

I used "detach" in old computer with running SQL SERVER 2000 and copy the
A.MDF file to the new computer with SQL Server 2005.
Then used "attach" to restore the database A in the new computer. The
database A still keeps the user names and machine name. I can not delete the
m.
The problem is that I can not expand the folder of Database Diagrams. When I
do it, I got the 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
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 did the "use the Files page of Database Properties dialog box to to set
the database owner to a valid login", by using a new computer valid user
name. But it does not work. I do not know how "then add the database diagram
support objects" either.
Thanks for any help.
Dabin>I used "detach" in old computer with running SQL SERVER 2000 and copy the
> A.MDF file to the new computer with SQL Server 2005.
OK, should be fine.

> Then used "attach" to restore the database A in the new computer. The
> database A still keeps the user names and machine name. I can not delete them.[/vb
col]
User names are expected. Yes, you can remove these if you wish. Check out DR
OP USER.
SQL Server does not store the machine name inside the database, except for t
he master and msdb
databases.
[vbcol=seagreen]
> The problem is that I can not expand the folder of Database Diagrams. When
I
> do it, I got the 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
> 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.
You need to set the owner to a login that exists as a login inside SQL Serve
r. After that is done
(and restart SSMS just in case), SSMS will add the procedures etc automatica
lly.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"david" <david@.discussions.microsoft.com> wrote in message
news:4838E101-064B-4658-8F73-85696E7FB195@.microsoft.com...
>I used "detach" in old computer with running SQL SERVER 2000 and copy the
> A.MDF file to the new computer with SQL Server 2005.
> Then used "attach" to restore the database A in the new computer. The
> database A still keeps the user names and machine name. I can not delete t
hem.
> The problem is that I can not expand the folder of Database Diagrams. When
I
> do it, I got the 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
> 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 did the "use the Files page of Database Properties dialog box to to set
> the database owner to a valid login", by using a new computer valid user
> name. But it does not work. I do not know how "then add the database diagr
am
> support objects" either.
> Thanks for any help.
> Dabin|||Thank you, Tibor:
My problem is the last one "You need to set the owner to a login that exists
as a login inside SQL Server. After that is done
(and restart SSMS just in case), SSMS will add the procedures etc
automatically.
--
"
I did something wrong.
I login to computer system, computer, by using my account, for example,
david. So the full name: computer\david.
I used SSMS to connect the database dbase. I right click on the database and
select the Properties. In the popup window, select Files. In the owner bos,
browser my account name, computer\david. Then click OK.
Restart SSMS. Tried to open the database diagrams, and I got the same error
massage.
David
"Tibor Karaszi" wrote:

> OK, should be fine.
>
> User names are expected. Yes, you can remove these if you wish. Check out
DROP USER.
> SQL Server does not store the machine name inside the database, except for
the master and msdb
> databases.
>
> You need to set the owner to a login that exists as a login inside SQL Ser
ver. After that is done
> (and restart SSMS just in case), SSMS will add the procedures etc automati
cally.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "david" <david@.discussions.microsoft.com> wrote in message
> news:4838E101-064B-4658-8F73-85696E7FB195@.microsoft.com...
>|||IT seems you did set the owner to a valid login. You could try to set the ow
ner to "sa" and see if
that helps. If not, I'm out of ideas, I'm afraid.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"david" <david@.discussions.microsoft.com> wrote in message
news:7F6BE323-F22F-42E1-846F-3CB685913381@.microsoft.com...[vbcol=seagreen]
> Thank you, Tibor:
> My problem is the last one "You need to set the owner to a login that exis
ts
> as a login inside SQL Server. After that is done
> (and restart SSMS just in case), SSMS will add the procedures etc
> automatically.
> --
> "
> I did something wrong.
> I login to computer system, computer, by using my account, for example,
> david. So the full name: computer\david.
> I used SSMS to connect the database dbase. I right click on the database a
nd
> select the Properties. In the popup window, select Files. In the owner bos
,
> browser my account name, computer\david. Then click OK.
> Restart SSMS. Tried to open the database diagrams, and I got the same erro
r
> massage.
> David
> "Tibor Karaszi" wrote:
>|||Hi David,
I got the same error and fixed it by
right click on database
properties
files
options
Then change the compatibility from 80 which is SQL2000 to 90 which is
SQL2005.
"Tibor Karaszi" wrote:

> IT seems you did set the owner to a valid login. You could try to set the
owner to "sa" and see if
> that helps. If not, I'm out of ideas, I'm afraid.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "david" <david@.discussions.microsoft.com> wrote in message
> news:7F6BE323-F22F-42E1-846F-3CB685913381@.microsoft.com...
>