Could not obtain exclusive lock on database ‘model’. Retry the operation later. CREATE DATABASE failed

After installing a SQL server 2008 R2 instance SQL_SERVER\MSSQLSERVER2008R2 side by side on the Box which already has SQL 2005 production instance, we are unable to create a database from the management studio   Receiving the below error   Create failed for Database ‘x’. (Microsoft.SqlServer.Smo) —————————— ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL…


There is insufficient system memory in resource pool ‘internal’ to run this query. Error: 701, Severity: 17, State: 123" on SSB Target Server – CACHESTORE_BROKERTO is consuming memory

I recently worked with a customer where the Target server for his Service broker application encounters “There is insufficient system memory in resource pool ‘internal’ to run this query. Error: 701, Severity: 17, State: 123” CACHESTORE_BROKERTO was consuming about 18 GB of RAM and SQL server is running out of memory.   Environment: ================== SQL:…


Service Pack Setup completes successfully on clustered instance but SQL Server Version is not updated on one node

I recently worked on an issue where one of my customers had successfully finished patching their SQL 2005 instances on a 3 node cluster. However the Build number was not getting updated on one of the nodes (NODE3) even after successfully completing the SP4 installation  SQL version On problem node: Database Services (INSTANCEX) SP3 2005.090.4340.00 …

SQL Server 2008 Add node setup hangs for hours at “Install SQL_DTS_VSTAConfiguration_install_Cpu64: RollbackCleanup: Removing backup files”

We recently encountered a situation while trying to ‘Add a node’ to the SQL 2008 Cluster The installation hung for hours at Install SQL_DTS_VSTAConfiguration_install_Cpu64: RollbackCleanup: Removing backup files It may also hang at Install_VS_Shell_Cpu32_Action: RollbackCleanup: Removing backup files We do not see any error messages from the SQL setup, however the setup just hangs and…


SQL Agent skipping Scheduled job runs!!– But the Job History does not reveal anything!

A Scheduled SQL Agent job skipped a Scheduled run on one particular day and the DBA wanted to investigate the root cause as he did not see any error messages or Job failures reported! This Job was used to collect some information and upload the data at regular intervals for the DBA’s customers to use….