Link to home
Start Free TrialLog in
Avatar of lapucca
lapucca

asked on

SSMS Database Diagrams error

Hi, I'm using sql 2012
I turned off all sql services, except for servcies of SQL SERVER, SQL SERVER VSS WRITER and SSDP DISCOVERY.  I then open SSMS, and the diagram I previously created for this database is not there.  I right click on the Database Diagrms node, menu shows options for "New Database diagram" and "Install diagram support"

Selecting either of these 2 menu options would give me the following error message.  However, when I examine the property of the database, it shows me already is the owner of the database.  

Is there a sql service that I need to turn back on ?  How t fix this?  Thank you.

TITLE: Microsoft SQL Server Management Studio
------------------------------

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.

------------------------------
BUTTONS:

OK
------------------------------
ASKER CERTIFIED SOLUTION
Avatar of Deepak Chauhan
Deepak Chauhan
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of lapucca
lapucca

ASKER

Deepak,
I followed your instruction except the alter command, which I didn't run, and it still worked! It bought back my diagram and I'm able to edit the diagram.  So what happened to my diagram before?  Is it because I turned off some SQL services?  I want to free up resources on my local dev pd so I turned off most sql services I dont' need.  Is this the cause of my problem?
Thank you.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of lapucca

ASKER

I didn't change or migrated the database.  It's odd but hopefully it wont' happen again, thank you.