All,I'm in the opening stages of a SharePoint deployment and today decided to rename all the existing databases to form a convention following the steps here:http://blogs.msdn.com/johnwpowell/archive/2009/12/15/sharepoint-database-naming-standards.aspxAfterwards, the Config DB, Central Admin and SSP all seem to be working, however I have a problem with the Timer service.About every 30 seconds it reports in the Application Event Log that it's unable to connect to SharePoint_Config on <SQL Server Name>, however the SharePoint_Config database no longer exists as I renamed it.How can I reconfigure the Timer service to use the correct Configuration database name? I looked at the stsadm parameters but can't find anything.ThanksRichard Richard Green, MCSA Windows Server 2003

I just found a link to this article for clearing the Timer cache.http://blogs.msdn.com/josrod/archive/2007/12/12/clear-the-sharepoint-configuration-cache-for-timer-job-and-psconfig-errors.aspxI followed the steps and have cleared the cache and I still have the same problem.Richard Green, MCSA Windows Server 2003

Here is a copy of one of the events in the log. SQL Database 'SharePoint_Config' on SQL Server instance 'SQL FQDN' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config" requested by the login. The login failed.Log Name: ApplicationSource: Windows SharePoint ServiceEvent ID: 3760Level: ErrorTask Category: Database Richard Green, MCSA Windows Server 2003

This is the output in the SharePoint log in %CommonProgramFiles%\Microsoft Shared\Web Server Extensions\12\LOGS02/02/2010 15:30:00.46 OWSTIMER.EXE (0x05EC) 0x0D3C Windows SharePoint Services Database 6f8e Critical SQL Database 'SharePoint_Config' on SQL Server instance 'SQL FQDN' not found. Additional error information from SQL Server is included below. Cannot open database "SharePoint_Config" requested by the login. The login failed.Richard Green, MCSA Windows Server 2003

Another question then would perhaps be this. Is renaming the SharePoint_Config database supported in this fashion? Am I going to be better off / easier to just name the database back to SharePoint_Config and then use the STSGUI to change the server to use the old DB name?Richard Green, MCSA Windows Server 2003

Hi Richard, Renaming the SharePoint DBs (actually the Configuration DB is the problem) is not a recommended thing. Refer to the following KB article for further details: Support for changes to the databases that are used by Office server products and by Windows SharePoint Services http://support.microsoft.com/kb/841057/en-us I am not sure you can name the database back to SharePoint_Config to fix the issue. You can try it. In my opinion, you need to rebuild your SharePoint configuration database and attach the content databases. For more information about renaming SharePoint Databases – A Cautionary Tale, please refer to the following blog: Renaming SharePoint Databases – A Cautionary Tale http://blogs.msdn.com/dstfs/archive/2009/05/14/renaming-sharepoint-databases-a-cautionary-tale.aspx Hope this helps. Rock Wang Rock Wang– MSFT