Today the next version of SQL Server is released. Most of us know that MS is working on SQL Server 2008 R2 and the last package released for this version is on November and we got the Nov CTP package. If you remember, on Jan 2010 DPI has posted a blog that SQL 2008 R2 will be May 2010 however MS has launched SQL Server 2008 R2 RTM today. SQL Server 2008 R2 packed with many features for BI, DBA’s and Developers. If you are express edition user then you have a good news, SQL Server 2008 R2 express edition supports max of 10 GB data file size which is increased from 4 GB however all other features remains same as SQL Server 2008 Express. We have couple of new editions also available for SQL Server 2008
Monthly Archives: April 2010
Backup SQL Database to Remote location
Posted by Vidhya Sagar
on April 10, 2010
No comments
Does the title sounds crazy? You might think that this topic is very simple? Yes you are right however some folks still raise this question in forums. I’m seeing this question for for a long time in forums and thought of sharing the solution here, so that the folks can give a search to get this (coz Google is our first techie teacher or instant solution provider 
).
Capture SQL Performance Counters through TSQL
Posted by Vidhya Sagar
on April 9, 2010
5 comments
Performance counters are useful to gather information about server status and we can analyze the server status later using these data. In my environment one of my client is not ready to pay or buy metrics tools (normally we will be using BMC, HP etc). Our windows team has written they own custom scripts to capture the counters related to them, then it comes to our team how we are going to capture these data. Immediately it strikes my mind that we have a DMV “sys.dm_os_performance_counters” to get SQL performance counter values. So I thought of utilizing this procedure to get SQL Performance counter values and storing it in a table which will help us in the future to analyze the data.
Suppress Backup information in Errorlog
Posted by Vidhya Sagar
on April 4, 2010
3 comments
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.