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 recovery. Show all posts
Showing posts with label recovery. 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
Thursday, March 22, 2012
diff. between simple and full recovery
Hi all,
do anyone know what is the different between simple and full recovery mode
in database properties.
thanksI suggest you search for the terms in Books Online. They are well described
there. Very short:
Full recovery mode allow you to perform transaction log backups. When you pe
rform transaction log
backup, the transaction log will be emptied.
In simple recovery mode, SQL Server will empty ("truncate) the transaction l
og for you, and
transaction log backup is not possible.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"BCat" <elin@.abcmultiactive.com> wrote in message news:ePUzahQCFHA.2384@.TK2MSFTNGP14.phx.gb
l...
> Hi all,
> do anyone know what is the different between simple and full recovery mode
> in database properties.
> thanks
>
>
do anyone know what is the different between simple and full recovery mode
in database properties.
thanksI suggest you search for the terms in Books Online. They are well described
there. Very short:
Full recovery mode allow you to perform transaction log backups. When you pe
rform transaction log
backup, the transaction log will be emptied.
In simple recovery mode, SQL Server will empty ("truncate) the transaction l
og for you, and
transaction log backup is not possible.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"BCat" <elin@.abcmultiactive.com> wrote in message news:ePUzahQCFHA.2384@.TK2MSFTNGP14.phx.gb
l...
> Hi all,
> do anyone know what is the different between simple and full recovery mode
> in database properties.
> thanks
>
>
Wednesday, March 21, 2012
Diff between SQL server and SQL server Personal edition
Hi All,
I would like to install SQL server 2000 personal edition
on a workstation as a backup to my server. (disaster
recovery scenario) I run a backup to this machine already
every 30 minutes, all I would have to do is turn on SQL
services, restore the latest backup and I am back up and
running within a few minutes. The workstaion has a 2 GIG
processor and 256 Ram which I am planning on upgrading to
512.
Are there any downsides to running 6 clients hitting this
personal edition server? Is the PE the same as the server
edition? Does the personal edition have limitations that
the server edition does not?
Thanks,
GPThanks,
Yes I know Windows prof. has a conection limitation, but
are there any SQL limitations running on a workstation?
Thanks again for your input.
GP|||The technical differences between editions are listed in Books Online (see the architecture
section). I suggest you call MS to make sure you aren't violating the licensing agreement:
To speak to someone regarding licensing:
You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
A.M. to 6:00 P.M. (PST) to speak directly to a Microsoft licensing
specialist for licensing problem. Worldwide customers can use the Guide to
Worldwide Microsoft Licensing Sites
http://www.microsoft.com/licensing/index/worldwide.asp to find contact
information in their locations.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"georgeP" <anonymous@.discussions.microsoft.com> wrote in message
news:493c01c49f24$18fc1830$a601280a@.phx.gbl...
> Thanks,
> Yes I know Windows prof. has a conection limitation, but
> are there any SQL limitations running on a workstation?
> Thanks again for your input.
> GP|||Hi
Just remember that a worstation edition of Windows (XP or 2000 Pro) both
have a limit of 10 concurrent client connections.
Regards
Mike
"GeorgeP" wrote:
> Hi All,
> I would like to install SQL server 2000 personal edition
> on a workstation as a backup to my server. (disaster
> recovery scenario) I run a backup to this machine already
> every 30 minutes, all I would have to do is turn on SQL
> services, restore the latest backup and I am back up and
> running within a few minutes. The workstaion has a 2 GIG
> processor and 256 Ram which I am planning on upgrading to
> 512.
> Are there any downsides to running 6 clients hitting this
> personal edition server? Is the PE the same as the server
> edition? Does the personal edition have limitations that
> the server edition does not?
> Thanks,
> GP
>sql
I would like to install SQL server 2000 personal edition
on a workstation as a backup to my server. (disaster
recovery scenario) I run a backup to this machine already
every 30 minutes, all I would have to do is turn on SQL
services, restore the latest backup and I am back up and
running within a few minutes. The workstaion has a 2 GIG
processor and 256 Ram which I am planning on upgrading to
512.
Are there any downsides to running 6 clients hitting this
personal edition server? Is the PE the same as the server
edition? Does the personal edition have limitations that
the server edition does not?
Thanks,
GPThanks,
Yes I know Windows prof. has a conection limitation, but
are there any SQL limitations running on a workstation?
Thanks again for your input.
GP|||The technical differences between editions are listed in Books Online (see the architecture
section). I suggest you call MS to make sure you aren't violating the licensing agreement:
To speak to someone regarding licensing:
You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
A.M. to 6:00 P.M. (PST) to speak directly to a Microsoft licensing
specialist for licensing problem. Worldwide customers can use the Guide to
Worldwide Microsoft Licensing Sites
http://www.microsoft.com/licensing/index/worldwide.asp to find contact
information in their locations.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"georgeP" <anonymous@.discussions.microsoft.com> wrote in message
news:493c01c49f24$18fc1830$a601280a@.phx.gbl...
> Thanks,
> Yes I know Windows prof. has a conection limitation, but
> are there any SQL limitations running on a workstation?
> Thanks again for your input.
> GP|||Hi
Just remember that a worstation edition of Windows (XP or 2000 Pro) both
have a limit of 10 concurrent client connections.
Regards
Mike
"GeorgeP" wrote:
> Hi All,
> I would like to install SQL server 2000 personal edition
> on a workstation as a backup to my server. (disaster
> recovery scenario) I run a backup to this machine already
> every 30 minutes, all I would have to do is turn on SQL
> services, restore the latest backup and I am back up and
> running within a few minutes. The workstaion has a 2 GIG
> processor and 256 Ram which I am planning on upgrading to
> 512.
> Are there any downsides to running 6 clients hitting this
> personal edition server? Is the PE the same as the server
> edition? Does the personal edition have limitations that
> the server edition does not?
> Thanks,
> GP
>sql
Monday, March 19, 2012
Diaster Recovery - Different Build Numbers
I have to test for a diaster recovery plan (in case the
building burned down) We do a full backup of the data
files on our SQL Server 2000 nightly. (Using Veritas with
SQL client) My job is to build a new server and restore
the databases. All is find until I try to restore the
master. Then I get the error that the build numbers are
different. I have applied all the service packs and
patches that I believe to be on the original box, but
cannot get the build numbers to match. Does MS list what
patches or updates are in which build numbers?
ThanksChris,
See if this helps
SQLSecurity Checklist
http://www.sqlsecurity.com/DesktopDefault.aspx?tabindex=3&tabid=4
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Chris" <chris.mcbirney@.go.doe.gov> wrote in message
news:581b01c376ff$9a59f2b0$a501280a@.phx.gbl...
> I have to test for a diaster recovery plan (in case the
> building burned down) We do a full backup of the data
> files on our SQL Server 2000 nightly. (Using Veritas with
> SQL client) My job is to build a new server and restore
> the databases. All is find until I try to restore the
> master. Then I get the error that the build numbers are
> different. I have applied all the service packs and
> patches that I believe to be on the original box, but
> cannot get the build numbers to match. Does MS list what
> patches or updates are in which build numbers?
> Thanks
building burned down) We do a full backup of the data
files on our SQL Server 2000 nightly. (Using Veritas with
SQL client) My job is to build a new server and restore
the databases. All is find until I try to restore the
master. Then I get the error that the build numbers are
different. I have applied all the service packs and
patches that I believe to be on the original box, but
cannot get the build numbers to match. Does MS list what
patches or updates are in which build numbers?
ThanksChris,
See if this helps
SQLSecurity Checklist
http://www.sqlsecurity.com/DesktopDefault.aspx?tabindex=3&tabid=4
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Chris" <chris.mcbirney@.go.doe.gov> wrote in message
news:581b01c376ff$9a59f2b0$a501280a@.phx.gbl...
> I have to test for a diaster recovery plan (in case the
> building burned down) We do a full backup of the data
> files on our SQL Server 2000 nightly. (Using Veritas with
> SQL client) My job is to build a new server and restore
> the databases. All is find until I try to restore the
> master. Then I get the error that the build numbers are
> different. I have applied all the service packs and
> patches that I believe to be on the original box, but
> cannot get the build numbers to match. Does MS list what
> patches or updates are in which build numbers?
> Thanks
Subscribe to:
Comments (Atom)