We have one 3 Node cluster with 1 SQL 2005 and 1 SQL 2008 R2 instance.

1.	We have one 3 Node cluster with 1 SQL 2005 and 1 SQL 2008 R2 instance. How many minimum installations are needed to patch all SQL instances in the cluster?
Answer» Full backups are SET of the complete database with all data. AT the time of any crash or data recovery it’s the starting point to select which full to sue to plan recovery path. To make THINGS CLEAR and doubt free, SQL Server INCLUDES all data or transactions data into full backup till the END TIME of backup.If your backup took 2 hours that backup will also contain data changes and transaction happen in this 2 hours. A full backup includes all data and transaction at the completion of backup time.The full backup cover complete transaction with all the changes that were made after the backup start checkpoint to apply those changes during the database recovery PROCESS.

We have one 3 Node cluster with 1 SQL 2005 and 1 SQL 2008 R2 instance. How many minimum installations are needed to patch all SQL instances in the cluster?

Answer»

Full backups are SET of the complete database with all data. AT the time of any crash or data recovery it’s the starting point to select which full to sue to plan recovery path.

To make THINGS CLEAR and doubt free, SQL Server INCLUDES all data or transactions data into full backup till the END TIME of backup.If your backup took 2 hours that backup will also contain data changes and transaction happen in this 2 hours.

A full backup includes all data and transaction at the completion of backup time.The full backup cover complete transaction with all the changes that were made after the backup start checkpoint to apply those changes during the database recovery PROCESS.

Discussion

No Comment Found

Related InterviewSolutions

What is .TUF file? What is the significance of the same? Any implications if the file is deleted?
Full backup size is 300 GB, usually my diff backup size varies between 300 MB and 5 GB, unfortunately, one-day diff backup size was increased to 250 GB? What might be the reason any idea?
See I have an environment, Sunday night full backup, everyday night diff backup, and every 45 min a transactional backup. The disaster happened at 2:30 PM on Saturday. You suddenly found that the last Sunday backup has been corrupted. What’s your recovery plan?
I wanted to know what are the maximum worker threads setting and active worker thread count on SQL server. Can you tell me how to capture this info? What’s the default value for the max thread count?
How distributed transactions work in SQL Server?
Can we add an article to the existing publication without generating a snapshot with all articles?
Consider a situation where publisher database log file has been increasing and there is just a few MB available on disk. As an experienced professional how do you react to this situation? Remember no disk space available and also we can’t create a new log file on another drive
When should a developer use the NOLOCK hint? What problems can happen when using this hint and how can these problems be addressed?
What is an optimistic and pessimistic lock in SQL?
What is Lock escalation in SQL