Click here to download presentation on this topic.
Often i notice that many skilled and seasoned DBA lack a guide line to share their knowledge with the online DBA community. By using the several free services, tools and plugins it is now very easy to access the knowledge base of your interest and also to share your knowledge with the whole community.
I am utilizing the community aspects of DBA since 2008 and found it a very valuable feature for every IT professional. So i arranged webinar in my organization (Systems Ltd) to motivate and guide my fellow DBAs and Developers towards a path where they start utilizing the community content as well as actively add their own efforts towards the community through blogs, articles, webcasts, presentations and webinars etc.
Due to my own background my presentation was slightly inclined to SQL Server DBAs but i made sure that it should be general enough to be adoptable by all DBAs and Devs. Today the webinar went quite successful. DBAs and Devs across various Systems Ltd offices participated and showed their eagerness towards all the points mentioned in the webinar.
Click here to download the presentation.
We all are involved with Microsoft products and MS has shown wonderful improvement in all its products. Obviously a very dedicated teamwork is behind all this improvement. And what if you get a chance to learn from those skillful and handwork resources who are part of products success. It will be a great deal of course. So here is a link that will lead you to lot of quality and focused videos on various Microsoft products and technologies. Watch online or download the short videos.
If you are new to DBA career or did not spend enough time on SQL Server Query Tuning skills then here is a right stuff to start with. As licensing models are changing and adding hardware also associates the licensing costs along with the hardware cost itself so fine tuning the queries and procedures is a required skill for DBAs.
You can download about 6 hours of training videos related to SQL Server Query Tuning skills. Videos are equipped with theory and demos side by side. These training videos are prepared for SQL Sentry by
SQL Server uses logical devices or media to perform database backups. Backups may be append or overwrite to existing backups in these media sets or devices. It may be a serious issue when a backup in device is silently overwritten without your notice. This scenario may occur if you repeat a previous backup device name with INIT option. Consider the following example for this scenario
-- Create a backup BACKUP DATABASE DBDIGGER TO DISK = 'E:DBD-BackupDemo.bak' GO /* Create another backup with same device name. By default backup would be performed by using WITH NOINIT option and would be appended */ BACKUP DATABASE DBDIGGER TO DISK = 'E:DBD-BackupDemo.bak' GO -- Verify the two backups on backup device RESTORE HEADERONLY FROM DISK = 'E:DBD-BackupDemo.bak' GO
Here we are shown two backups on the device. It shows that second backup was also appended to the device. Going further we would issue another backup command by using WITH INIT. This time backup would overwrite the existing backups on the device.
/* Create another backup with same device name and INIT option. It would overwrite the existing backups on device. */ BACKUP DATABASE DBDIGGER TO DISK = 'E:DBD-BackupDemo.bak' WITH INIT GO
Now verify that only last backup exists on the device and all previous backups were overwritten.
/* Verify that previous backups are overwritten leaving behind the last backup */ RESTORE HEADERONLY FROM DISK = 'E:DBD-BackupDemo.bak' GO
RETAINING THE BACKUPS ON THE DEVICE
- Use WITH EXPIREDATE or WITH RETAINDAYS
- Set retention days server wide for all databases
Following is a brief description of these two options
WITH EXPIREDATE | WITH RETAINDAYS days
This option operates along with backup command for a specific device of a database. We may specify a date or days along with WITH EXPIREDATE or WITH RETAINDAYS option respectively. Here we would create a backup device with retention span of two days
-- Create a backup with retention span 2 days BACKUP DATABASE DBDIGGER TO DISK = 'E:DBD-BackupDemo2.bak' WITH RETAINDAYS = 2 GO
Now create a backup in same device along with using WITH INIT option. This time error would be generated because backups in the device are retained for two days.
/* Create another backup with same device name and INIT option. It would overwrite the existing backups on device. */ BACKUP DATABASE DBDIGGER TO DISK = 'E:DBD-BackupDemo2.bak' WITH INIT GO
If next backups are created in the device without any retention parameter even then device would maintain the backups with retention parameter and could not be overwritten for next two days. We may get the expiration date or retention span of files by using RESTORE HEADERONLY.
Similarly EXPIREDATE option may be used to specify an expiration date to which backups on the device would be retained. Date provided should be according to system configured date format.
SET RETENTION DAYS AT SERVER LEVEL
We have another option to include the fixed retention days for every backup device of databases on that very server. For using this method
- Right click on instance
- Go to properties
- Go to database settings in the left panel
- Set default media retention span in days here. By default it is zero
The retention days span here would automatically be implemented for every backup device of that server without explicit use of EXPIREDATE or RETAINDAYS.
Although WITH INIT would not be able to overwrite the retained media but WITH FORMAT may overwrite the header and content of device.
Each of SQL Server release like SQL Server 2000, SQL Server 2005 and SQL Server 2008 is further categorized in editions based on their features and capabilities. For example, edition of a specific release may be any of following
Apart from these there may be some other editions like run time edition or web edition. Some editions like Data center edition or enterprise edition can only be installed on Server OS while others may be installed on both server or client OS.
For windows platform the term Server OS refers to different editions of
While for windows platform, client OS would be any edition of following
So while installing any SQL Server version, do consult the requirements related to OS.