Suppress Backup information in Errorlog
After a long gap I’m writing a article. This article is all about suppressing successful backup information into errorlog. Let me explain my scenario, In my working environment we have a production SQL Server with 60+ databases, all the databases are set to full recovery and data loss is accepted only for 15 min. Yeah you got me, we are taking Full backup daily, differential every 4 hours and transaction log backup every 15 min, there is no problem with the backup. We have one thing that is messing our error log, whenever a backup is taken by default SQL Server will write the detail to the errorlog as shown below.
DotNet 3.5 on Windows 7 to Install SQL Server 2008
This is a quick post to install or enable .Net 3.5 on windows 7. Last couple of weeks I’m seeing more questions on installing SQL Server 2008 in windows 7 and the users are unable to install SQL Server 2008 pre-requisite (.Net 3.5 ). To Install SQL Server 2008, windows installer 4.5 & .Net 3.5 is required. Windows installer 4.5 is installed and enabled by default, .Net 3.5 is included in windows features, so you can directly go there and turn on .Net 3.5, windows 7 will automatically install this. To turn on .Net 3.5 in Windows 7 just follow the steps below
Error: 7139, Severity: 16, State: 1 – failed to upload large sized file to db
Last week in our company we have started facing some error while uploading documents to the table. We have an database in which we will be uploading all the documents related to the customers, when the user tries to upload the document he \ she gets the error message as shown below
Connection to the target machine could not be made in a timely fashion – SSCM
Problem:
In our cluster environment I was testing SQL failover, when I failed over to passive node I can no longer launch SQL Server configuration manager (SSCM). When I tried to open SSCM, MMC has waited for 30 seconds and gave me the error below.
“Connection to target machine could not be made in a timely fashion”
Resolution:
Upon researching on this I found that WMI Service (Windows Management Instrumentation Service) is in hanged state. After restarting the service on passive node, it worked for me. Steps to restart the service is below.
- Go to Run –> type services.msc and press enter
- Right click on the service “Windows Management Instrumentation” and click on restart option in the menu
- Now launch SQL Server configuration manager, it should work fine now.
SQL Backup on NTFS Compressed folder
I’m starting this topic since last week I had faced a backup issue with compressed drive. In one of our server we have used compressed folder to take backup of our SQL databases. This is working fine and the db is used for OLTP application and it had grown about 73GB. Now we have started facing backup failures only for that database alone all other databases (less than 10GB) are running fine in the maintenance plan. I’ve checked the machine performance and SQL Server is the only process using 50% of CPU and 3GB of memory, other than that the server is not under stress and in fact that box is dedicated to SQL Server.