![]() ![]() With the same error message repeated over and over, it would be difficult to sift through the log and a DBA could miss other errors or warnings.Things would be even worse for instances where the log was not cycled regularly. Even with this instance where the Error Log was cycled every night, it was still taking time to load thousands of rows of log entries. The potentially large Error Log would take longer and longer to load.In other words, disk access would be almost continuous. If this was a production server, SQL would be spending I/O time writing the same message to the Error Log.The reason I wanted to dig deeper was because the error was happening many times, almost every ten seconds, and in my view it had these potential problems: The server was running an instance of SQL Server 2008 and although it was a test instance, I decided to spend some time to find out what database was being accessed by this account. It could also be the default database for the login where explicit permission was not given. The database could be offline, shutdown, deleted, dropped, renamed, auto-closed, or inaccessible for some other reason. As I found out later, States 38 and 40 (in SQL 2008 and later) and States 16 and 27 (before version 2008) mean that there is an issue with the database being connected to. Like other error messages, it also has a State number and there are different State numbers associated with it, each having a different meaning for the failure. ![]() ![]() Įrror 18456 generally means a failed login attempt. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |