Comments for D B A N A T I O N http://www.dbanation.com Maninder's SQL Server Blog Wed, 28 Apr 2010 18:29:40 -0400 hourly 1 http://wordpress.org/?v=3.0.1 Comment on Download SQL Server SystemTable Posters by Tweets that mention Download SQL Server SystemTable Posters » D B A N A T I O N -- Topsy.com http://www.dbanation.com/?p=463&cpage=1#comment-80 Tweets that mention Download SQL Server SystemTable Posters » D B A N A T I O N -- Topsy.com Wed, 28 Apr 2010 18:29:40 +0000 http://www.dbanation.com/?p=463#comment-80 [...] This post was mentioned on Twitter by MANINDER. MANINDER said: Download SQL Server system Table Posters: http://lnkd.in/M2qSpF [...] [...] This post was mentioned on Twitter by MANINDER. MANINDER said: Download SQL Server system Table Posters: http://lnkd.in/M2qSpF [...]

]]> Comment on Lets Talk Disaster Recovery – Backup & Restore by maninder http://www.dbanation.com/?p=405&cpage=1#comment-44 maninder Sun, 07 Mar 2010 20:07:25 +0000 http://www.dbanation.com/?p=405#comment-44 Christo, There are many possibilities and you mention one of them. But the scenario i am talking about is the most common used across organizations and a simple one with out any filegroups and or otherwise or a corruption. In case of filegroups yes we can backup filegroups etc... but my point across this scenario was to explain, how and what to restore in case of a simple process. but yes good points to put across.. Christo, There are many possibilities and you mention one of them. But the scenario i am talking about is the most common used across organizations and a simple one with out any filegroups and or otherwise or a corruption.
In case of filegroups yes we can backup filegroups etc… but my point across this scenario was to explain, how and what to restore in case of a simple process.
but yes good points to put across..

]]> Comment on Lets Talk Disaster Recovery – Backup & Restore by Christo Pretorius http://www.dbanation.com/?p=405&cpage=1#comment-43 Christo Pretorius Sun, 07 Mar 2010 18:07:28 +0000 http://www.dbanation.com/?p=405#comment-43 A step is missing with this process. If you can access the current corrupt database, backup the transaction log first before you start restoring from the last full backup. More information can be found here: http://technet.microsoft.com/en-us/library/dd297499.aspx Also note that you have the option to backup file groups if your database size reach a point where normal weekly full and daily differential backups can't fit in the maintenance window for backups. This can become complicated but with planning and test restore executions you would find that it is a straight forward process. A step is missing with this process. If you can access the current corrupt database, backup the transaction log first before you start restoring from the last full backup. More information can be found here:
http://technet.microsoft.com/en-us/library/dd297499.aspx

Also note that you have the option to backup file groups if your database size reach a point where normal weekly full and daily differential backups can’t fit in the maintenance window for backups. This can become complicated but with planning and test restore executions you would find that it is a straight forward process.

]]> Comment on Lets Talk Disaster Recovery – Backup & Restore by maninder http://www.dbanation.com/?p=405&cpage=1#comment-41 maninder Fri, 05 Mar 2010 20:49:08 +0000 http://www.dbanation.com/?p=405#comment-41 I Agree Robert. There are ways to explain a things. I Wrote this because i had just finished explaining this concept to my fellow DBA's in APP Department. I am surprised as to how ignorant or still confused those DBA's are even after earning their MCDBA and MCTS. But hey thanks for the Inputs and i have changed the BLOG likewise. I Agree Robert. There are ways to explain a things. I Wrote this because i had just finished explaining this concept to my fellow DBA’s in APP Department. I am surprised as to how ignorant or still confused those DBA’s are even after earning their MCDBA and MCTS.
But hey thanks for the Inputs and i have changed the BLOG likewise.

]]> Comment on Lets Talk Disaster Recovery – Backup & Restore by Robert L Davis http://www.dbanation.com/?p=405&cpage=1#comment-40 Robert L Davis Fri, 05 Mar 2010 20:41:26 +0000 http://www.dbanation.com/?p=405#comment-40 Good article. The following statement is correct, but I believe that it's meaning my be misunderstood: The transaction logs will contain all the changes that occurred from the latest differential backup and thereafter each log back contains changes that occurred since last transaction log backup. I understand what you are saying, but someone with less knowledge ont he subject may not. Log backups are functionally ignorant of differential backups. But the way a log restore works is that it will start recovering from the point of the last restored LSN .... even though the log backup may contain data that goes back much further than differential backup. For example, if a log backup runs at 10:00 AM, a differential backup runs at 10:30 AM, and the next log backup runs at 11:00 AM, the 11:00 AM backup will contain all changes since 10:00 AM, the previous log backup. If you are restoring the database and restore the 10:30 AM differential backup and then the 11:00 AM log backup, the log backup restore will start processing data at the next LSN in the log backup after the last LSN that restored from the differential backup. I hope I made it more clear instead of more confusing!! :) Also, some people find it easier to perform the restore in this order: Restore the Latest Full Backup WITH NORECOVERY Restore the Latest Differential Backup WITH NORECOVERY Restore the all the Transaction Log Backups since the Latest Differential Backup WITH NORECOVERY. Execute RESTORE BACKUP WITH RECOVERY; The key point to take away from that approach is that if you forget to use WITH RECOVERY ont eh final transaction log, you don't have to re-run the entire restore process. You can simply run the restore command WITH RECOVERY without specifying a backup file and it will complete the recovery process. Good article.

The following statement is correct, but I believe that it’s meaning my be misunderstood: The transaction logs will contain all the changes that occurred from the latest differential backup and thereafter each log back contains changes that occurred since last transaction log backup.

I understand what you are saying, but someone with less knowledge ont he subject may not. Log backups are functionally ignorant of differential backups. But the way a log restore works is that it will start recovering from the point of the last restored LSN …. even though the log backup may contain data that goes back much further than differential backup.

For example, if a log backup runs at 10:00 AM, a differential backup runs at 10:30 AM, and the next log backup runs at 11:00 AM, the 11:00 AM backup will contain all changes since 10:00 AM, the previous log backup. If you are restoring the database and restore the 10:30 AM differential backup and then the 11:00 AM log backup, the log backup restore will start processing data at the next LSN in the log backup after the last LSN that restored from the differential backup.

I hope I made it more clear instead of more confusing!! :)

Also, some people find it easier to perform the restore in this order:

Restore the Latest Full Backup WITH NORECOVERY
Restore the Latest Differential Backup WITH NORECOVERY
Restore the all the Transaction Log Backups since the Latest Differential Backup WITH NORECOVERY.
Execute RESTORE BACKUP WITH RECOVERY;

The key point to take away from that approach is that if you forget to use WITH RECOVERY ont eh final transaction log, you don’t have to re-run the entire restore process. You can simply run the restore command WITH RECOVERY without specifying a backup file and it will complete the recovery process.

]]> Comment on Rename a SQL Server Column (Several Columns at once) by Remove Double Quotes or Weird characters from All SQL Server Columns at once using T-SQL « DBANATION – SQLServer Blog http://www.dbanation.com/?p=232&cpage=1#comment-26 Remove Double Quotes or Weird characters from All SQL Server Columns at once using T-SQL « DBANATION – SQLServer Blog Fri, 15 Jan 2010 12:20:28 +0000 http://dbanation.com/?p=232#comment-26 [...] A similar article i wrote about re-naming the columns with double quotes HERE [...] [...] A similar article i wrote about re-naming the columns with double quotes HERE [...]

]]> Comment on SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 1 (Database Move) by SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 2 (Database Check) « DBANATION – SQLServer Blog http://www.dbanation.com/?p=192&cpage=1#comment-23 SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 2 (Database Check) « DBANATION – SQLServer Blog Tue, 29 Dec 2009 16:12:00 +0000 http://dbanation.com/?p=192#comment-23 [...] Resume « SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part ... [...] [...] Resume « SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part … [...]

]]> Comment on SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 2 (Database Check) by SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 1 (Database Move) « DBANATION – SQLServer Blog http://www.dbanation.com/?p=196&cpage=1#comment-22 SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 1 (Database Move) « DBANATION – SQLServer Blog Tue, 29 Dec 2009 16:10:59 +0000 http://dbanation.com/?p=196#comment-22 [...] « Reading a SQL Server Error Log SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part ... [...] [...] « Reading a SQL Server Error Log SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part … [...]

]]> Comment on Orphaned Database users (issues and solutions) by SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 2 (Database Check) « DBANATION – SQLServer Blog http://www.dbanation.com/?p=60&cpage=1#comment-21 SQL Server Database migration from SQL Server 2000 to 2005/2008 as easy as it can get. – Part 2 (Database Check) « DBANATION – SQLServer Blog Tue, 29 Dec 2009 16:08:05 +0000 http://dbanation.com/?p=60#comment-21 [...] After Creating/Moving the Logins/users, check for orphaned users with : Read here [...] [...] After Creating/Moving the Logins/users, check for orphaned users with : Read here [...]

]]> Comment on Reading a SQL Server Error Log by dba_beginner http://www.dbanation.com/?p=152&cpage=1#comment-20 dba_beginner Mon, 28 Dec 2009 15:29:10 +0000 http://dbanation.com/?p=152#comment-20 Great Post!!! Great Post!!!

]]>