Database Diagram Support Objects cannot be Installed … no valid owner

后端 未结 14 1225
醉酒成梦
醉酒成梦 2021-01-29 18:22

I tried to create a database diagramm with SQL Server 2008, but an error occurs:

Database diagram support objects cannot be installed because this dat

相关标签:
14条回答
  • 2021-01-29 19:05

    1.Right click on your Database , 2.Then select properties . 3.Select the option in compatibility levels choose sql 2008[100] if you are working with Microsoft sql 2008.

    4.Then select the file and write ( sa ) in owner`s textbox

    100% works for me.

    0 讨论(0)
  • 2021-01-29 19:09

    Enter "SA" instead of "sa" in the owner textbox. This worked for me.

    0 讨论(0)
  • 2021-01-29 19:09

    Select your database - Right Click - Select Properties

    Select FILE in left side of page

    In the OWNER box, select button which has three dots (…) in it

    Now select user ‘sa and Click OK

    0 讨论(0)
  • 2021-01-29 19:12

    An easier way to solve this issues would be to right click the name of your database, choose "New Query", type " exec sp_changedbowner 'sa' " and execute the query. Then you'll be good to go.

    0 讨论(0)
  • 2021-01-29 19:12

    right click on your Database , then select properties . select the option in compatibility levels choose sql 2005[90] instead of 2008 if you are working with Microsoft sql 2008. then select the file and write ( sa ) in owner`s textbox. it will work probably

    0 讨论(0)
  • 2021-01-29 19:13

    You should consider SQL authentication account for database ownership; then you don't have to worry about accounts coming and going, databases or instances moving to different servers, and your next PC name change. I have several systems where we use:

    ALTER AUTHORIZATION ON DATABASE::Ariha TO [sa];
    

    Or if you want to change the owner to that local Administrator account, then it should be:

    ALTER AUTHORIZATION ON DATABASE::Ariha TO [DevPC\Administrator];
    

    Because renaming the machine to DevPC has eliminated the local account that used to be named WIN-ND...\Administrator and this has also invalidated the current owner of the database.

    If SELECT @@SERVERNAME; is not accurate (it should say DevPC), then in order to ensure that your server rename has taken hold within SQL Server, you may also want to issue the following:

    EXEC sys.sp_dropserver @server = N'old server name';
    GO
    EXEC sys.sp_addserver @server = N'DevPC', @local = N'local';
    GO
    
    0 讨论(0)
提交回复
热议问题