Our application works with sql server 2008 R2 enterprise edition. This server has around 315 databases used by the application and in this server Sql Backups are configured. The SQL Backups are just doing a normal VDI backup (i.e. using SQL Server's built-in
mechanisms). The application is developed using .NET 3.5 and is deployed in IIS 7.0
One of the requirements is to port old sql databases to work with the new version of the application which requires running scripts for altering/removing/creating tables, constraints, Stored Procedures, Views, Indexes etc from the application. We use SMO to
run scripts. This was working fine previously. Recently we found that when the scripts are run from the program, it is failing.
The errors that are logged from the application are given below,
1) A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
2) Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
3)A network-related or instance-specific error occurred while establishi
View Complete Post