Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Property Collation is not available for Database Expand / Collapse
Author
Message
Posted Sunday, January 27, 2013 9:19 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 1:49 PM
Points: 65, Visits: 590
Backup job failed last night - viewing the history logs gave the following message "Could not find database ID 15. Database may not be activated yet or may be in transition"

Going to the database I tried to review the properties and got the following message:

Property Collation is not available for Database '[xxxx]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)

There have been no changes to this database in quite some time. This is a 2008 SQL Server enterprise edition 64 bit environment. Any comments / URLs would be appreciated.

Thank you
Post #1412135
Posted Sunday, January 27, 2013 12:35 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 1:49 PM
Points: 65, Visits: 590
This is a followup to this issue. Running query SP_HELPDB does not list the database with it's owner. The query does provide the following message:
No permission to access database 'database name'.

Any comments / URLs would be appreciated.
Post #1412145
Posted Sunday, January 27, 2013 1:22 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, September 18, 2014 7:56 AM
Points: 6,723, Visits: 8,462
check your sqlserver errorlog file to see what it is reporting about that database.
Keep in mind, you may have to process more than one errorlog file to get to the first occurence of its reporting errors for that database.


Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #1412146
Posted Sunday, January 27, 2013 11:19 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:23 PM
Points: 114, Visits: 1,222
From the error description, it indicates that:

Your test database uses case-insensitive collation, where your prod database uses case-sensitive collation.

The error indicates that SQL cannot find the specified database.

Please verify that the database name used in the script EXACTLY matches the actual database name, including case.

If it doesn't already, have the script print out the value of the database name as the script is executing.


SQL Database Recovery Expert
Post #1412191
Posted Thursday, June 5, 2014 7:42 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Sunday, August 31, 2014 1:00 AM
Points: 464, Visits: 1,036
I see this is a old post but I got the similar error today and I got it fixed through just taking the database offline and bring online. I got this error twice now and got it fixed the same way.





--SQLFRNDZ
Post #1578124
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse