So you’ve got a Microsoft Access database with linked tables to a SQL server that looks something like this.
When opening one of the linked table you get an error that says, “ODBC–connection to ‘DP’ failed”.
When you click OK you get a message that says, “Microsoft Access can’t open the table in Datasheet view”.
Hmm, what up with the ODBC connection called “DP”? What say you Procmon?
Result = NAME NOT FOUND. Oh, the ODBC connection doesn’t exist. Create the ODBC connection & you are good to go.
I admit that you could have also just gone & looked at the ODBC connections in the Control Panel to figure out it doesn’t exist but it was really just an excuse to use Procmon.
After installing SQL 2008 SP3 I started getting hundreds of these event log entries.
Event ID: 17137
Description: Starting up database ‘AdventureWorks2008’.
This is due to the AUTO_CLOSE option being turned on. To read more about that setting have a look at the link below. Long story short…you don’t want it on.
To fix the issue open SQL Server Management Studio. Right click the database that is being logged in the error & select Properties. Select Options. Set Auto Close to False. Click OK. No more error. Repeat as needed for other databases.
You can use SQL Server Management Studio Express (SQL SMSE) to connect to the internal WSUS database. Do the following.
- If not already done, Install SQL SMSE 2005.
- Launch SQL SMSE.
- In the Server name drop-down type \\.\pipe\mssql$microsoft##ssee\sql\query
- In the Authentication drop-down select Windows Authentication.
- You can now use SQL SMSE to run queries against the WSUS database (SUSBD).
- Browse to C:\Documents and Settings\username\Application Data\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM.
- Rename mru.dat to mru.bak
- Now open SQL Server Management Studio Express & the Server name dropdown will be empty.