what is the difference between Full recovery, Bulk-logged, Simple recoveryhi joe
full recovery means the entire db is recovered
bulk logged means part of the log is recovered
certain bulk operations are not recovered
refer teach urself in 21 days by sams
"Joe" wrote:
> what is the difference between Full recovery, Bulk-logged, Simple recovery|||Under bulk-logged recovery model, once you do a log backup, all extents that
were allocated as part bulk-logged operations are backed up. So potentially
your transaction log can be huge. The only caveat is that you cannot do
point-in-time recovery from a log backup that contains bulk-logged
operations. But you can always recover at the transaction log boundary (i.e.
you can apply the full log that contains bulk-logged operations).
thanks
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"raghu veer" <raghuveer@.discussions.microsoft.com> wrote in message
news:D304EEF7-FB2A-478E-B2FF-0A5343D5446B@.microsoft.com...[vbcol=seagreen]
> hi joe
> full recovery means the entire db is recovered
> bulk logged means part of the log is recovered
> certain bulk operations are not recovered
> refer teach urself in 21 days by sams
> "Joe" wrote:
>|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:81E7D411-8776-40B4-B3C4-A4B1B020CEDD@.microsoft.com...
> what is the difference between Full recovery, Bulk-logged, Simple recovery
Are you serious'
Why do you need to know?
Did you get a job as a SQL Server DBA without knowing this? Scary. Go to you
boss' office and hand in your resignation.
Is it a homework question for school? Are you so lazy and incompetent that
you cannot be arsed to research this by yourself?
You are a disgrace.
Foz
Showing posts with label bulk-logged. Show all posts
Showing posts with label bulk-logged. Show all posts
Tuesday, March 27, 2012
Difference between Full recovery, Bulk-logged, Simple recovery
Difference between Full recovery, Bulk-logged, Simple recoveryHi,
1. SIMPLE:-
Transaction log will be cleraed automatically after the checkpoint and hence
backup of transaction log is not possible. So we can
recover the database only until last full database backup
2. BULK LOGGED:-
Transaction log will be cleared only after the log backup but the below
operations are minimally logged.
SELECT INTO.
Bulk load operations (bcp and BULK INSERT).
CREATE INDEX (including indexed views).
Text and image operations
So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
3. FULL:-
Logs all the activites inside the database and with the help of
transactionlog backup you can recover the database point in time.
NOTE:-
For BULK LOGGED and FULL recovery model ensure that the log backup is
happening (enough room in hard disk), otherwise the
transaction log will grow and will eat the full harddisk space and will
create downtime.
Thanks
Hari
SQL Server MVP
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> Difference between Full recovery, Bulk-logged, Simple recovery|||If i use full backup, but the point - in -time check box is disable once
restoration
"Hari Prasad" wrote:
> Hi,
> 1. SIMPLE:-
> Transaction log will be cleraed automatically after the checkpoint and hen
ce
> backup of transaction log is not possible. So we can
> recover the database only until last full database backup
> 2. BULK LOGGED:-
> Transaction log will be cleared only after the log backup but the below
> operations are minimally logged.
> SELECT INTO.
> Bulk load operations (bcp and BULK INSERT).
> CREATE INDEX (including indexed views).
> Text and image operations
> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
> 3. FULL:-
> Logs all the activites inside the database and with the help of
> transactionlog backup you can recover the database point in time.
> NOTE:-
> For BULK LOGGED and FULL recovery model ensure that the log backup is
> happening (enough room in hard disk), otherwise the
> transaction log will grow and will eat the full harddisk space and will
> create downtime.
> Thanks
> Hari
> SQL Server MVP
>
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
>
>|||Point in time applies to processing the transaction log during restore to a
particular point in time.
You must take a transaction log and then this option will be available.
Nik Marshall-Blank MCSD/MCDBA
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:035E79B4-2E80-4198-9FA7-F9DB8307E078@.microsoft.com...[vbcol=seagreen]
> If i use full backup, but the point - in -time check box is disable once
> restoration
> "Hari Prasad" wrote:
>
1. SIMPLE:-
Transaction log will be cleraed automatically after the checkpoint and hence
backup of transaction log is not possible. So we can
recover the database only until last full database backup
2. BULK LOGGED:-
Transaction log will be cleared only after the log backup but the below
operations are minimally logged.
SELECT INTO.
Bulk load operations (bcp and BULK INSERT).
CREATE INDEX (including indexed views).
Text and image operations
So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
3. FULL:-
Logs all the activites inside the database and with the help of
transactionlog backup you can recover the database point in time.
NOTE:-
For BULK LOGGED and FULL recovery model ensure that the log backup is
happening (enough room in hard disk), otherwise the
transaction log will grow and will eat the full harddisk space and will
create downtime.
Thanks
Hari
SQL Server MVP
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> Difference between Full recovery, Bulk-logged, Simple recovery|||If i use full backup, but the point - in -time check box is disable once
restoration
"Hari Prasad" wrote:
> Hi,
> 1. SIMPLE:-
> Transaction log will be cleraed automatically after the checkpoint and hen
ce
> backup of transaction log is not possible. So we can
> recover the database only until last full database backup
> 2. BULK LOGGED:-
> Transaction log will be cleared only after the log backup but the below
> operations are minimally logged.
> SELECT INTO.
> Bulk load operations (bcp and BULK INSERT).
> CREATE INDEX (including indexed views).
> Text and image operations
> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
> 3. FULL:-
> Logs all the activites inside the database and with the help of
> transactionlog backup you can recover the database point in time.
> NOTE:-
> For BULK LOGGED and FULL recovery model ensure that the log backup is
> happening (enough room in hard disk), otherwise the
> transaction log will grow and will eat the full harddisk space and will
> create downtime.
> Thanks
> Hari
> SQL Server MVP
>
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
>
>|||Point in time applies to processing the transaction log during restore to a
particular point in time.
You must take a transaction log and then this option will be available.
Nik Marshall-Blank MCSD/MCDBA
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:035E79B4-2E80-4198-9FA7-F9DB8307E078@.microsoft.com...[vbcol=seagreen]
> If i use full backup, but the point - in -time check box is disable once
> restoration
> "Hari Prasad" wrote:
>
Difference between Full recovery, Bulk-logged, Simple recovery
what is the difference between Full recovery, Bulk-logged, Simple recoveryhi joe
full recovery means the entire db is recovered
bulk logged means part of the log is recovered
certain bulk operations are not recovered
refer teach urself in 21 days by sams
"Joe" wrote:
> what is the difference between Full recovery, Bulk-logged, Simple recovery|||Under bulk-logged recovery model, once you do a log backup, all extents that
were allocated as part bulk-logged operations are backed up. So potentially
your transaction log can be huge. The only caveat is that you cannot do
point-in-time recovery from a log backup that contains bulk-logged
operations. But you can always recover at the transaction log boundary (i.e.
you can apply the full log that contains bulk-logged operations).
thanks
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"raghu veer" <raghuveer@.discussions.microsoft.com> wrote in message
news:D304EEF7-FB2A-478E-B2FF-0A5343D5446B@.microsoft.com...
> hi joe
> full recovery means the entire db is recovered
> bulk logged means part of the log is recovered
> certain bulk operations are not recovered
> refer teach urself in 21 days by sams
> "Joe" wrote:
>> what is the difference between Full recovery, Bulk-logged, Simple
>> recovery|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:81E7D411-8776-40B4-B3C4-A4B1B020CEDD@.microsoft.com...
> what is the difference between Full recovery, Bulk-logged, Simple recovery
Are you serious'
Why do you need to know?
Did you get a job as a SQL Server DBA without knowing this? Scary. Go to you
boss' office and hand in your resignation.
Is it a homework question for school? Are you so lazy and incompetent that
you cannot be arsed to research this by yourself?
You are a disgrace.
Fozsql
full recovery means the entire db is recovered
bulk logged means part of the log is recovered
certain bulk operations are not recovered
refer teach urself in 21 days by sams
"Joe" wrote:
> what is the difference between Full recovery, Bulk-logged, Simple recovery|||Under bulk-logged recovery model, once you do a log backup, all extents that
were allocated as part bulk-logged operations are backed up. So potentially
your transaction log can be huge. The only caveat is that you cannot do
point-in-time recovery from a log backup that contains bulk-logged
operations. But you can always recover at the transaction log boundary (i.e.
you can apply the full log that contains bulk-logged operations).
thanks
--
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"raghu veer" <raghuveer@.discussions.microsoft.com> wrote in message
news:D304EEF7-FB2A-478E-B2FF-0A5343D5446B@.microsoft.com...
> hi joe
> full recovery means the entire db is recovered
> bulk logged means part of the log is recovered
> certain bulk operations are not recovered
> refer teach urself in 21 days by sams
> "Joe" wrote:
>> what is the difference between Full recovery, Bulk-logged, Simple
>> recovery|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:81E7D411-8776-40B4-B3C4-A4B1B020CEDD@.microsoft.com...
> what is the difference between Full recovery, Bulk-logged, Simple recovery
Are you serious'
Why do you need to know?
Did you get a job as a SQL Server DBA without knowing this? Scary. Go to you
boss' office and hand in your resignation.
Is it a homework question for school? Are you so lazy and incompetent that
you cannot be arsed to research this by yourself?
You are a disgrace.
Fozsql
Difference between Full recovery, Bulk-logged, Simple recovery
Difference between Full recovery, Bulk-logged, Simple recoveryHi,
1. SIMPLE:-
Transaction log will be cleraed automatically after the checkpoint and hence
backup of transaction log is not possible. So we can
recover the database only until last full database backup
2. BULK LOGGED:-
Transaction log will be cleared only after the log backup but the below
operations are minimally logged.
SELECT INTO.
Bulk load operations (bcp and BULK INSERT).
CREATE INDEX (including indexed views).
Text and image operations
So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
3. FULL:-
Logs all the activites inside the database and with the help of
transactionlog backup you can recover the database point in time.
NOTE:-
For BULK LOGGED and FULL recovery model ensure that the log backup is
happening (enough room in hard disk), otherwise the
transaction log will grow and will eat the full harddisk space and will
create downtime.
Thanks
Hari
SQL Server MVP
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> Difference between Full recovery, Bulk-logged, Simple recovery|||If i use full backup, but the point - in -time check box is disable once
restoration
"Hari Prasad" wrote:
> Hi,
> 1. SIMPLE:-
> Transaction log will be cleraed automatically after the checkpoint and hence
> backup of transaction log is not possible. So we can
> recover the database only until last full database backup
> 2. BULK LOGGED:-
> Transaction log will be cleared only after the log backup but the below
> operations are minimally logged.
> SELECT INTO.
> Bulk load operations (bcp and BULK INSERT).
> CREATE INDEX (including indexed views).
> Text and image operations
> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
> 3. FULL:-
> Logs all the activites inside the database and with the help of
> transactionlog backup you can recover the database point in time.
> NOTE:-
> For BULK LOGGED and FULL recovery model ensure that the log backup is
> happening (enough room in hard disk), otherwise the
> transaction log will grow and will eat the full harddisk space and will
> create downtime.
> Thanks
> Hari
> SQL Server MVP
>
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> > Difference between Full recovery, Bulk-logged, Simple recovery
>
>|||Point in time applies to processing the transaction log during restore to a
particular point in time.
You must take a transaction log and then this option will be available.
--
Nik Marshall-Blank MCSD/MCDBA
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:035E79B4-2E80-4198-9FA7-F9DB8307E078@.microsoft.com...
> If i use full backup, but the point - in -time check box is disable once
> restoration
> "Hari Prasad" wrote:
>> Hi,
>> 1. SIMPLE:-
>> Transaction log will be cleraed automatically after the checkpoint and
>> hence
>> backup of transaction log is not possible. So we can
>> recover the database only until last full database backup
>> 2. BULK LOGGED:-
>> Transaction log will be cleared only after the log backup but the below
>> operations are minimally logged.
>> SELECT INTO.
>> Bulk load operations (bcp and BULK INSERT).
>> CREATE INDEX (including indexed views).
>> Text and image operations
>> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
>> 3. FULL:-
>> Logs all the activites inside the database and with the help of
>> transactionlog backup you can recover the database point in time.
>> NOTE:-
>> For BULK LOGGED and FULL recovery model ensure that the log backup is
>> happening (enough room in hard disk), otherwise the
>> transaction log will grow and will eat the full harddisk space and will
>> create downtime.
>> Thanks
>> Hari
>> SQL Server MVP
>>
>> "Joe" <Joe@.discussions.microsoft.com> wrote in message
>> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
>> > Difference between Full recovery, Bulk-logged, Simple recovery
>>
1. SIMPLE:-
Transaction log will be cleraed automatically after the checkpoint and hence
backup of transaction log is not possible. So we can
recover the database only until last full database backup
2. BULK LOGGED:-
Transaction log will be cleared only after the log backup but the below
operations are minimally logged.
SELECT INTO.
Bulk load operations (bcp and BULK INSERT).
CREATE INDEX (including indexed views).
Text and image operations
So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
3. FULL:-
Logs all the activites inside the database and with the help of
transactionlog backup you can recover the database point in time.
NOTE:-
For BULK LOGGED and FULL recovery model ensure that the log backup is
happening (enough room in hard disk), otherwise the
transaction log will grow and will eat the full harddisk space and will
create downtime.
Thanks
Hari
SQL Server MVP
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> Difference between Full recovery, Bulk-logged, Simple recovery|||If i use full backup, but the point - in -time check box is disable once
restoration
"Hari Prasad" wrote:
> Hi,
> 1. SIMPLE:-
> Transaction log will be cleraed automatically after the checkpoint and hence
> backup of transaction log is not possible. So we can
> recover the database only until last full database backup
> 2. BULK LOGGED:-
> Transaction log will be cleared only after the log backup but the below
> operations are minimally logged.
> SELECT INTO.
> Bulk load operations (bcp and BULK INSERT).
> CREATE INDEX (including indexed views).
> Text and image operations
> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
> 3. FULL:-
> Logs all the activites inside the database and with the help of
> transactionlog backup you can recover the database point in time.
> NOTE:-
> For BULK LOGGED and FULL recovery model ensure that the log backup is
> happening (enough room in hard disk), otherwise the
> transaction log will grow and will eat the full harddisk space and will
> create downtime.
> Thanks
> Hari
> SQL Server MVP
>
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> > Difference between Full recovery, Bulk-logged, Simple recovery
>
>|||Point in time applies to processing the transaction log during restore to a
particular point in time.
You must take a transaction log and then this option will be available.
--
Nik Marshall-Blank MCSD/MCDBA
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:035E79B4-2E80-4198-9FA7-F9DB8307E078@.microsoft.com...
> If i use full backup, but the point - in -time check box is disable once
> restoration
> "Hari Prasad" wrote:
>> Hi,
>> 1. SIMPLE:-
>> Transaction log will be cleraed automatically after the checkpoint and
>> hence
>> backup of transaction log is not possible. So we can
>> recover the database only until last full database backup
>> 2. BULK LOGGED:-
>> Transaction log will be cleared only after the log backup but the below
>> operations are minimally logged.
>> SELECT INTO.
>> Bulk load operations (bcp and BULK INSERT).
>> CREATE INDEX (including indexed views).
>> Text and image operations
>> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
>> 3. FULL:-
>> Logs all the activites inside the database and with the help of
>> transactionlog backup you can recover the database point in time.
>> NOTE:-
>> For BULK LOGGED and FULL recovery model ensure that the log backup is
>> happening (enough room in hard disk), otherwise the
>> transaction log will grow and will eat the full harddisk space and will
>> create downtime.
>> Thanks
>> Hari
>> SQL Server MVP
>>
>> "Joe" <Joe@.discussions.microsoft.com> wrote in message
>> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
>> > Difference between Full recovery, Bulk-logged, Simple recovery
>>
Sunday, March 25, 2012
Difference between Full recovery, Bulk-logged, Simple recovery
Difference between Full recovery, Bulk-logged, Simple recovery
Hi,
1. SIMPLE:-
Transaction log will be cleraed automatically after the checkpoint and hence
backup of transaction log is not possible. So we can
recover the database only until last full database backup
2. BULK LOGGED:-
Transaction log will be cleared only after the log backup but the below
operations are minimally logged.
SELECT INTO.
Bulk load operations (bcp and BULK INSERT).
CREATE INDEX (including indexed views).
Text and image operations
So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
3. FULL:-
Logs all the activites inside the database and with the help of
transactionlog backup you can recover the database point in time.
NOTE:-
For BULK LOGGED and FULL recovery model ensure that the log backup is
happening (enough room in hard disk), otherwise the
transaction log will grow and will eat the full harddisk space and will
create downtime.
Thanks
Hari
SQL Server MVP
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> Difference between Full recovery, Bulk-logged, Simple recovery
|||If i use full backup, but the point - in -time check box is disable once
restoration
"Hari Prasad" wrote:
> Hi,
> 1. SIMPLE:-
> Transaction log will be cleraed automatically after the checkpoint and hence
> backup of transaction log is not possible. So we can
> recover the database only until last full database backup
> 2. BULK LOGGED:-
> Transaction log will be cleared only after the log backup but the below
> operations are minimally logged.
> SELECT INTO.
> Bulk load operations (bcp and BULK INSERT).
> CREATE INDEX (including indexed views).
> Text and image operations
> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
> 3. FULL:-
> Logs all the activites inside the database and with the help of
> transactionlog backup you can recover the database point in time.
> NOTE:-
> For BULK LOGGED and FULL recovery model ensure that the log backup is
> happening (enough room in hard disk), otherwise the
> transaction log will grow and will eat the full harddisk space and will
> create downtime.
> Thanks
> Hari
> SQL Server MVP
>
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
>
>
|||Point in time applies to processing the transaction log during restore to a
particular point in time.
You must take a transaction log and then this option will be available.
Nik Marshall-Blank MCSD/MCDBA
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:035E79B4-2E80-4198-9FA7-F9DB8307E078@.microsoft.com...[vbcol=seagreen]
> If i use full backup, but the point - in -time check box is disable once
> restoration
> "Hari Prasad" wrote:
Hi,
1. SIMPLE:-
Transaction log will be cleraed automatically after the checkpoint and hence
backup of transaction log is not possible. So we can
recover the database only until last full database backup
2. BULK LOGGED:-
Transaction log will be cleared only after the log backup but the below
operations are minimally logged.
SELECT INTO.
Bulk load operations (bcp and BULK INSERT).
CREATE INDEX (including indexed views).
Text and image operations
So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
3. FULL:-
Logs all the activites inside the database and with the help of
transactionlog backup you can recover the database point in time.
NOTE:-
For BULK LOGGED and FULL recovery model ensure that the log backup is
happening (enough room in hard disk), otherwise the
transaction log will grow and will eat the full harddisk space and will
create downtime.
Thanks
Hari
SQL Server MVP
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
> Difference between Full recovery, Bulk-logged, Simple recovery
|||If i use full backup, but the point - in -time check box is disable once
restoration
"Hari Prasad" wrote:
> Hi,
> 1. SIMPLE:-
> Transaction log will be cleraed automatically after the checkpoint and hence
> backup of transaction log is not possible. So we can
> recover the database only until last full database backup
> 2. BULK LOGGED:-
> Transaction log will be cleared only after the log backup but the below
> operations are minimally logged.
> SELECT INTO.
> Bulk load operations (bcp and BULK INSERT).
> CREATE INDEX (including indexed views).
> Text and image operations
> So POINT_IN_TIME recovery isnot possible in BULK LOGGED mode
> 3. FULL:-
> Logs all the activites inside the database and with the help of
> transactionlog backup you can recover the database point in time.
> NOTE:-
> For BULK LOGGED and FULL recovery model ensure that the log backup is
> happening (enough room in hard disk), otherwise the
> transaction log will grow and will eat the full harddisk space and will
> create downtime.
> Thanks
> Hari
> SQL Server MVP
>
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:79078DFD-2D6B-4D0F-8DA9-947EC2A22D92@.microsoft.com...
>
>
|||Point in time applies to processing the transaction log during restore to a
particular point in time.
You must take a transaction log and then this option will be available.
Nik Marshall-Blank MCSD/MCDBA
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:035E79B4-2E80-4198-9FA7-F9DB8307E078@.microsoft.com...[vbcol=seagreen]
> If i use full backup, but the point - in -time check box is disable once
> restoration
> "Hari Prasad" wrote:
Difference between Full recovery, Bulk-logged, Simple recovery
what is the difference between Full recovery, Bulk-logged, Simple recovery
hi joe
full recovery means the entire db is recovered
bulk logged means part of the log is recovered
certain bulk operations are not recovered
refer teach urself in 21 days by sams
"Joe" wrote:
> what is the difference between Full recovery, Bulk-logged, Simple recovery
|||Under bulk-logged recovery model, once you do a log backup, all extents that
were allocated as part bulk-logged operations are backed up. So potentially
your transaction log can be huge. The only caveat is that you cannot do
point-in-time recovery from a log backup that contains bulk-logged
operations. But you can always recover at the transaction log boundary (i.e.
you can apply the full log that contains bulk-logged operations).
thanks
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"raghu veer" <raghuveer@.discussions.microsoft.com> wrote in message
news:D304EEF7-FB2A-478E-B2FF-0A5343D5446B@.microsoft.com...[vbcol=seagreen]
> hi joe
> full recovery means the entire db is recovered
> bulk logged means part of the log is recovered
> certain bulk operations are not recovered
> refer teach urself in 21 days by sams
> "Joe" wrote:
|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:81E7D411-8776-40B4-B3C4-A4B1B020CEDD@.microsoft.com...
> what is the difference between Full recovery, Bulk-logged, Simple recovery
Are you serious?
Why do you need to know?
Did you get a job as a SQL Server DBA without knowing this? Scary. Go to you
boss' office and hand in your resignation.
Is it a homework question for school? Are you so lazy and incompetent that
you cannot be arsed to research this by yourself?
You are a disgrace.
Foz
hi joe
full recovery means the entire db is recovered
bulk logged means part of the log is recovered
certain bulk operations are not recovered
refer teach urself in 21 days by sams
"Joe" wrote:
> what is the difference between Full recovery, Bulk-logged, Simple recovery
|||Under bulk-logged recovery model, once you do a log backup, all extents that
were allocated as part bulk-logged operations are backed up. So potentially
your transaction log can be huge. The only caveat is that you cannot do
point-in-time recovery from a log backup that contains bulk-logged
operations. But you can always recover at the transaction log boundary (i.e.
you can apply the full log that contains bulk-logged operations).
thanks
Sunil Agarwal (MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"raghu veer" <raghuveer@.discussions.microsoft.com> wrote in message
news:D304EEF7-FB2A-478E-B2FF-0A5343D5446B@.microsoft.com...[vbcol=seagreen]
> hi joe
> full recovery means the entire db is recovered
> bulk logged means part of the log is recovered
> certain bulk operations are not recovered
> refer teach urself in 21 days by sams
> "Joe" wrote:
|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:81E7D411-8776-40B4-B3C4-A4B1B020CEDD@.microsoft.com...
> what is the difference between Full recovery, Bulk-logged, Simple recovery
Are you serious?
Why do you need to know?
Did you get a job as a SQL Server DBA without knowing this? Scary. Go to you
boss' office and hand in your resignation.
Is it a homework question for school? Are you so lazy and incompetent that
you cannot be arsed to research this by yourself?
You are a disgrace.
Foz
Subscribe to:
Posts (Atom)