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
SQL Server Joins
SQL Server joins are required to retrieve data from one or more tables to get a single result set. Joins are needed when Normalization enforced in design. When you normalize the data you be reducing redundancy in data by placing data in different tables and also you will be creating relationship between the tables. With the help of these relationship you will be retrieving the data using joins efficiently.
Merge Drop Slipstream Setup – SQL Server 2008
In my previous article we have discussed about Basic slipstream setup, now I’m going to write a article on Merged Drop slipstream setup. In this method you will be merging the service pack with the base setup prior to the installation there by altering the source or base setup files. The merged setup package can be reused multiple times and you can burn it in DVD or copy it to a network share. However the main thing is that you need to TEST this setup package before promoting it as the core setup or live setup copy.