locked
property size is not available for database sql server 2012 RRS feed

  • Question

  • Database property size not available?
    • Edited by dbadays Friday, December 5, 2014 1:16 PM Unfair question
    Thursday, November 13, 2014 7:51 PM

Answers

  • Hello,

    Please change the owner to “sa” or make sure the owner of the database has not been eliminated from the SQL Server instance.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by Shanky_621MVP Monday, November 24, 2014 11:25 PM
    • Marked as answer by Donghui Li Wednesday, December 3, 2014 1:31 AM
    Monday, November 24, 2014 7:50 PM
  • Hi,

    What Alberto pointed could be one reason and I have seen such errors subsiding by making SA or a valid login as owner of database. Please note SA as owner of DB is not considered as best practice

    This issue can also occur if there is some corruption in Database I would ask you to check errorlog and see if you can find any relevant information


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My Technet Wiki Article

    MVP


    • Edited by Shanky_621MVP Monday, November 24, 2014 11:30 PM
    • Marked as answer by Donghui Li Wednesday, December 3, 2014 1:31 AM
    Monday, November 24, 2014 11:30 PM

All replies

  • Hello,

    Make sure the database has an owner specified as explained on the following resource:

    http://blogs.msdn.com/b/suhde/archive/2009/04/05/property-owner-is-not-available-for-database-dbname.aspx

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Thursday, November 13, 2014 8:02 PM
  • Hi Alberto

    The database owner has already assigned to the database.


    DBA

    Thursday, November 13, 2014 8:07 PM
  • Hello,

    Please change the owner to “sa” or make sure the owner of the database has not been eliminated from the SQL Server instance.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    • Proposed as answer by Shanky_621MVP Monday, November 24, 2014 11:25 PM
    • Marked as answer by Donghui Li Wednesday, December 3, 2014 1:31 AM
    Monday, November 24, 2014 7:50 PM
  • Have you tried sp_helpdb 'db_name' ? is there any long runing transaction or bulk operations currently ? have you checked the connection or open transaction details ? was there any interesting error messages in the error log ? Is this production server or test server ? if this is not a production then just restart the sql once and try...

    Raju Rasagounder Sr MSSQL DBA

    Monday, November 24, 2014 11:20 PM
  • Hi,

    What Alberto pointed could be one reason and I have seen such errors subsiding by making SA or a valid login as owner of database. Please note SA as owner of DB is not considered as best practice

    This issue can also occur if there is some corruption in Database I would ask you to check errorlog and see if you can find any relevant information


    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My Technet Wiki Article

    MVP


    • Edited by Shanky_621MVP Monday, November 24, 2014 11:30 PM
    • Marked as answer by Donghui Li Wednesday, December 3, 2014 1:31 AM
    Monday, November 24, 2014 11:30 PM