I am using a Full recovery model on SQL 2005 with a daily full and 15 min
transactional. The disk constantly keeps getting full and I have to manually
delete the .bak and .trn files that are three days old to allow for more disk
space. My first option was to only do a Full backup once a week and keep
transaction backups at 15 min. Regardless, I still have to have an automated
way to do this. Is there a way, tool, script somewhere that I could use to
manage this automatically? Thank you.
morphius wrote:
> I am using a Full recovery model on SQL 2005 with a daily full and 15 min
> transactional. The disk constantly keeps getting full and I have to manually
> delete the .bak and .trn files that are three days old to allow for more disk
> space. My first option was to only do a Full backup once a week and keep
> transaction backups at 15 min. Regardless, I still have to have an automated
> way to do this. Is there a way, tool, script somewhere that I could use to
> manage this automatically? Thank you.
http://realsqlguy.com/serendipity/archives/9-Out-With-The-Old.html
Note that this uses xp_cmdshell, so you'll need to enable that since
you're on SQL 2005.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Thanks
"Tracy McKibben" wrote:
> morphius wrote:
> http://realsqlguy.com/serendipity/archives/9-Out-With-The-Old.html
> Note that this uses xp_cmdshell, so you'll need to enable that since
> you're on SQL 2005.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>
|||Thanks
"Tibor Karaszi" wrote:
> Maintenance Plans can create new and delete old backup files. The feature of removing old backup
> files is not available in the wizard (until sp2), so make sure to edit the package to add such task.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "morphius" <morphius@.discussions.microsoft.com> wrote in message
> news:1A9D1A49-5BBA-4022-84FF-3158790E0B5C@.microsoft.com...
>
Showing posts with label model. Show all posts
Showing posts with label model. Show all posts
Thursday, March 8, 2012
Backups Question?
I am using a Full recovery model on SQL 2005 with a daily full and 15 min
transactional. The disk constantly keeps getting full and I have to manually
delete the .bak and .trn files that are three days old to allow for more dis
k
space. My first option was to only do a Full backup once a week and keep
transaction backups at 15 min. Regardless, I still have to have an automated
way to do this. Is there a way, tool, script somewhere that I could use to
manage this automatically? Thank you.morphius wrote:
> I am using a Full recovery model on SQL 2005 with a daily full and 15 min
> transactional. The disk constantly keeps getting full and I have to manual
ly
> delete the .bak and .trn files that are three days old to allow for more d
isk
> space. My first option was to only do a Full backup once a week and keep
> transaction backups at 15 min. Regardless, I still have to have an automat
ed
> way to do this. Is there a way, tool, script somewhere that I could use t
o
> manage this automatically? Thank you.
http://realsqlguy.com/serendipity/a...th-The-Old.html
Note that this uses xp_cmdshell, so you'll need to enable that since
you're on SQL 2005.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Maintenance Plans can create new and delete old backup files. The feature of
removing old backup
files is not available in the wizard (until sp2), so make sure to edit the p
ackage to add such task.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"morphius" <morphius@.discussions.microsoft.com> wrote in message
news:1A9D1A49-5BBA-4022-84FF-3158790E0B5C@.microsoft.com...
>I am using a Full recovery model on SQL 2005 with a daily full and 15 min
> transactional. The disk constantly keeps getting full and I have to manual
ly
> delete the .bak and .trn files that are three days old to allow for more d
isk
> space. My first option was to only do a Full backup once a week and keep
> transaction backups at 15 min. Regardless, I still have to have an automat
ed
> way to do this. Is there a way, tool, script somewhere that I could use t
o
> manage this automatically? Thank you.|||Thanks
"Tracy McKibben" wrote:
> morphius wrote:
> http://realsqlguy.com/serendipity/a...th-The-Old.html
> Note that this uses xp_cmdshell, so you'll need to enable that since
> you're on SQL 2005.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Thanks
"Tibor Karaszi" wrote:
> Maintenance Plans can create new and delete old backup files. The feature
of removing old backup
> files is not available in the wizard (until sp2), so make sure to edit the
package to add such task.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "morphius" <morphius@.discussions.microsoft.com> wrote in message
> news:1A9D1A49-5BBA-4022-84FF-3158790E0B5C@.microsoft.com...
>
transactional. The disk constantly keeps getting full and I have to manually
delete the .bak and .trn files that are three days old to allow for more dis
k
space. My first option was to only do a Full backup once a week and keep
transaction backups at 15 min. Regardless, I still have to have an automated
way to do this. Is there a way, tool, script somewhere that I could use to
manage this automatically? Thank you.morphius wrote:
> I am using a Full recovery model on SQL 2005 with a daily full and 15 min
> transactional. The disk constantly keeps getting full and I have to manual
ly
> delete the .bak and .trn files that are three days old to allow for more d
isk
> space. My first option was to only do a Full backup once a week and keep
> transaction backups at 15 min. Regardless, I still have to have an automat
ed
> way to do this. Is there a way, tool, script somewhere that I could use t
o
> manage this automatically? Thank you.
http://realsqlguy.com/serendipity/a...th-The-Old.html
Note that this uses xp_cmdshell, so you'll need to enable that since
you're on SQL 2005.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Maintenance Plans can create new and delete old backup files. The feature of
removing old backup
files is not available in the wizard (until sp2), so make sure to edit the p
ackage to add such task.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"morphius" <morphius@.discussions.microsoft.com> wrote in message
news:1A9D1A49-5BBA-4022-84FF-3158790E0B5C@.microsoft.com...
>I am using a Full recovery model on SQL 2005 with a daily full and 15 min
> transactional. The disk constantly keeps getting full and I have to manual
ly
> delete the .bak and .trn files that are three days old to allow for more d
isk
> space. My first option was to only do a Full backup once a week and keep
> transaction backups at 15 min. Regardless, I still have to have an automat
ed
> way to do this. Is there a way, tool, script somewhere that I could use t
o
> manage this automatically? Thank you.|||Thanks
"Tracy McKibben" wrote:
> morphius wrote:
> http://realsqlguy.com/serendipity/a...th-The-Old.html
> Note that this uses xp_cmdshell, so you'll need to enable that since
> you're on SQL 2005.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Thanks
"Tibor Karaszi" wrote:
> Maintenance Plans can create new and delete old backup files. The feature
of removing old backup
> files is not available in the wizard (until sp2), so make sure to edit the
package to add such task.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "morphius" <morphius@.discussions.microsoft.com> wrote in message
> news:1A9D1A49-5BBA-4022-84FF-3158790E0B5C@.microsoft.com...
>
Sunday, February 19, 2012
Backup/Restore File groups
I have a very large database(150G) with two filegroups.
One of the most frequent operation on this database is
bulk insert. The Recovery model is set to Simple for
avoiding the log file to grow. Since the db is so big I
need to individualy backup each file group and, in case
something happens, to be able to restore one filegroup. My
problem is that since I cannot afford to have recovery
model FULL, I don't have all the log backups required in
order to restore only one filegroup. There is any solution
to this problem?
Thank you
What exactly is the reason you can't back up a 150GB db? Is it disk space?
You may want to check out a product called SQL LiteSpeed that can compress
your backups down to 70 or 80%.
Andrew J. Kelly SQL MVP
"Laura" <anonymous@.discussions.microsoft.com> wrote in message
news:90ba01c43300$ad2b9e30$a001280a@.phx.gbl...
> I have a very large database(150G) with two filegroups.
> One of the most frequent operation on this database is
> bulk insert. The Recovery model is set to Simple for
> avoiding the log file to grow. Since the db is so big I
> need to individualy backup each file group and, in case
> something happens, to be able to restore one filegroup. My
> problem is that since I cannot afford to have recovery
> model FULL, I don't have all the log backups required in
> order to restore only one filegroup. There is any solution
> to this problem?
> Thank you
One of the most frequent operation on this database is
bulk insert. The Recovery model is set to Simple for
avoiding the log file to grow. Since the db is so big I
need to individualy backup each file group and, in case
something happens, to be able to restore one filegroup. My
problem is that since I cannot afford to have recovery
model FULL, I don't have all the log backups required in
order to restore only one filegroup. There is any solution
to this problem?
Thank you
What exactly is the reason you can't back up a 150GB db? Is it disk space?
You may want to check out a product called SQL LiteSpeed that can compress
your backups down to 70 or 80%.
Andrew J. Kelly SQL MVP
"Laura" <anonymous@.discussions.microsoft.com> wrote in message
news:90ba01c43300$ad2b9e30$a001280a@.phx.gbl...
> I have a very large database(150G) with two filegroups.
> One of the most frequent operation on this database is
> bulk insert. The Recovery model is set to Simple for
> avoiding the log file to grow. Since the db is so big I
> need to individualy backup each file group and, in case
> something happens, to be able to restore one filegroup. My
> problem is that since I cannot afford to have recovery
> model FULL, I don't have all the log backups required in
> order to restore only one filegroup. There is any solution
> to this problem?
> Thank you
Monday, February 13, 2012
Backup trouble with system database model
Hello all,
Al of a sudden I cannot backup my model database.
When I try to backup the database I get the following message:
Server: Msg 9002, Level 17, State 6, Line 1
The log file for database 'model' is full. Back up the transaction log for t
he database to free up some log space.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
Could not write a CHECKPOINT record in database ID 3 because the log is out
of space.
I have 2 questions:
(1) To my knowledge the model database has not been changed since the SQL se
rver installation (+/- 1 year ago), accept a weekly "Optimization". The mode
l database has recovery model "Simple". How did the log file get filled?
(2) How do I empty the log file? I have tried to empty the log file via:
--> DUMP TRANSACTION model WITH NO_LOG
--> BACKUP LOG model WITH NO_LOG
However with no success.
Any suggestion is welcome, thanks,
Annick van den BroekHi,
Have a look into this article;
http://support.microsoft.com/defaul...kb;en-us;317375
Thanks
Hari
MCDBA
"Annick van den Broek" <anonymous@.discussions.microsoft.com> wrote in
message news:5F6BC6C8-BFCD-4A7C-96A4-753A3F27AF12@.microsoft.com...
> Hello all,
> Al of a sudden I cannot backup my model database.
> When I try to backup the database I get the following message:
> Server: Msg 9002, Level 17, State 6, Line 1
> The log file for database 'model' is full. Back up the transaction log for
the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> Could not write a CHECKPOINT record in database ID 3 because the log is
out of space.
> I have 2 questions:
> (1) To my knowledge the model database has not been changed since the SQL
server installation (+/- 1 year ago), accept a weekly "Optimization". The
model database has recovery model "Simple". How did the log file get filled?
> (2) How do I empty the log file? I have tried to empty the log file via:
> --> DUMP TRANSACTION model WITH NO_LOG
> --> BACKUP LOG model WITH NO_LOG
> However with no success.
> Any suggestion is welcome, thanks,
> Annick van den Broek
Al of a sudden I cannot backup my model database.
When I try to backup the database I get the following message:
Server: Msg 9002, Level 17, State 6, Line 1
The log file for database 'model' is full. Back up the transaction log for t
he database to free up some log space.
Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
Could not write a CHECKPOINT record in database ID 3 because the log is out
of space.
I have 2 questions:
(1) To my knowledge the model database has not been changed since the SQL se
rver installation (+/- 1 year ago), accept a weekly "Optimization". The mode
l database has recovery model "Simple". How did the log file get filled?
(2) How do I empty the log file? I have tried to empty the log file via:
--> DUMP TRANSACTION model WITH NO_LOG
--> BACKUP LOG model WITH NO_LOG
However with no success.
Any suggestion is welcome, thanks,
Annick van den BroekHi,
Have a look into this article;
http://support.microsoft.com/defaul...kb;en-us;317375
Thanks
Hari
MCDBA
"Annick van den Broek" <anonymous@.discussions.microsoft.com> wrote in
message news:5F6BC6C8-BFCD-4A7C-96A4-753A3F27AF12@.microsoft.com...
> Hello all,
> Al of a sudden I cannot backup my model database.
> When I try to backup the database I get the following message:
> Server: Msg 9002, Level 17, State 6, Line 1
> The log file for database 'model' is full. Back up the transaction log for
the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 1
> BACKUP DATABASE is terminating abnormally.
> Could not write a CHECKPOINT record in database ID 3 because the log is
out of space.
> I have 2 questions:
> (1) To my knowledge the model database has not been changed since the SQL
server installation (+/- 1 year ago), accept a weekly "Optimization". The
model database has recovery model "Simple". How did the log file get filled?
> (2) How do I empty the log file? I have tried to empty the log file via:
> --> DUMP TRANSACTION model WITH NO_LOG
> --> BACKUP LOG model WITH NO_LOG
> However with no success.
> Any suggestion is welcome, thanks,
> Annick van den Broek
Sunday, February 12, 2012
Backup Transaction Log - Event ID 17055
I recently changed the recovery model from simple to full on a specific SQL
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts'?
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:
> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts'?
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.|||Yes, that has been completed.
"Hari Prasad" wrote:
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote:
> > I recently changed the recovery model from simple to full on a specific SQL
> > Server 2000 database. I am backing up the transaction log every two hours
> > via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> > full recovery model and do not receive these messages. The following error,
> > not a warning, appears in the application event log when the log backup
> > completes also in the database log. Are these backups valid? Found KB
> > 818202 on this, but I cannot determine what action needs to be taken, if any.
> > Thoughts'?
> >
> > Source: MSSQLSERVER
> > Category: (6)
> > Event ID: 17055
> > Description: 18278 Database log truncated: Database: dbname.|||It looks like someone is running a Backup LOG command with
NO_LOG or TRUNCATE_ONLY option. Investigate if anyone or
any job is scheduled to run this command. Also, check your
own backup log command to see if it includes this option.
Lll the Log backups after a truncate will be invalid till
you take a FULL backup.
>--Original Message--
>I recently changed the recovery model from simple to full
on a specific SQL
>Server 2000 database. I am backing up the transaction
log every two hours
>via a maintenance plan. I have other SQL Server 2000 DB's
defined with the
>full recovery model and do not receive these messages.
The following error,
>not a warning, appears in the application event log when
the log backup
>completes also in the database log. Are these backups
valid? Found KB
>818202 on this, but I cannot determine what action needs
to be taken, if any.
> Thoughts'?
>Source: MSSQLSERVER
>Category: (6)
>Event ID: 17055
>Description: 18278 Database log truncated: Database:
dbname.
>.
>
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts'?
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:
> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts'?
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.|||Yes, that has been completed.
"Hari Prasad" wrote:
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote:
> > I recently changed the recovery model from simple to full on a specific SQL
> > Server 2000 database. I am backing up the transaction log every two hours
> > via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> > full recovery model and do not receive these messages. The following error,
> > not a warning, appears in the application event log when the log backup
> > completes also in the database log. Are these backups valid? Found KB
> > 818202 on this, but I cannot determine what action needs to be taken, if any.
> > Thoughts'?
> >
> > Source: MSSQLSERVER
> > Category: (6)
> > Event ID: 17055
> > Description: 18278 Database log truncated: Database: dbname.|||It looks like someone is running a Backup LOG command with
NO_LOG or TRUNCATE_ONLY option. Investigate if anyone or
any job is scheduled to run this command. Also, check your
own backup log command to see if it includes this option.
Lll the Log backups after a truncate will be invalid till
you take a FULL backup.
>--Original Message--
>I recently changed the recovery model from simple to full
on a specific SQL
>Server 2000 database. I am backing up the transaction
log every two hours
>via a maintenance plan. I have other SQL Server 2000 DB's
defined with the
>full recovery model and do not receive these messages.
The following error,
>not a warning, appears in the application event log when
the log backup
>completes also in the database log. Are these backups
valid? Found KB
>818202 on this, but I cannot determine what action needs
to be taken, if any.
> Thoughts'?
>Source: MSSQLSERVER
>Category: (6)
>Event ID: 17055
>Description: 18278 Database log truncated: Database:
dbname.
>.
>
Backup Transaction Log - Event ID 17055
I recently changed the recovery model from simple to full on a specific SQL
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts??
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.
Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:
> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts??
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.
|||Yes, that has been completed.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote:
Server 2000 database. I am backing up the transaction log every two hours
via a maintenance plan. I have other SQL Server 2000 DB's defined with the
full recovery model and do not receive these messages. The following error,
not a warning, appears in the application event log when the log backup
completes also in the database log. Are these backups valid? Found KB
818202 on this, but I cannot determine what action needs to be taken, if any.
Thoughts??
Source: MSSQLSERVER
Category: (6)
Event ID: 17055
Description: 18278 Database log truncated: Database: dbname.
Hi,
Can you perform a full database backup and then follow the transaction log
backup.
This is required when you change the recovery model from SIMPLE to FULL
Thanks
Hari
MCDBA
"paldba" wrote:
> I recently changed the recovery model from simple to full on a specific SQL
> Server 2000 database. I am backing up the transaction log every two hours
> via a maintenance plan. I have other SQL Server 2000 DB's defined with the
> full recovery model and do not receive these messages. The following error,
> not a warning, appears in the application event log when the log backup
> completes also in the database log. Are these backups valid? Found KB
> 818202 on this, but I cannot determine what action needs to be taken, if any.
> Thoughts??
> Source: MSSQLSERVER
> Category: (6)
> Event ID: 17055
> Description: 18278 Database log truncated: Database: dbname.
|||Yes, that has been completed.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> Can you perform a full database backup and then follow the transaction log
> backup.
> This is required when you change the recovery model from SIMPLE to FULL
> Thanks
> Hari
> MCDBA
> "paldba" wrote:
Backup transaction log
Hi,
I have error when i backup the transaction log of master and msdb database.
I think there is an error because the model of this database is simple.
can i modify the model and write full ?
I have another question,
I have a db with 1 db file of 11Go, i have to create secondary files or not.No, you can't change the Model database.
No, you don't need to add secondary files, but it might be a good idea.
-PatP|||Are you using the enterprise manager?|||Master database doesn't allow Differential or log backups.
Post the error message that u get while backing up the transaction log for msdb.
Howdy!|||From the tool list go to shrink database; File; change shrink to transaction log. before implentation. Go out to network and very the log size. Then go back to EM and shrink log. Again go for verifaction.
Live from Dodge City USA, Washington DC|||Yes i using entreprise manager
the error i get for msdb is the following :
"La sauvegarde ne peut tre effectue sur cette base de donnes. Cette sous-tche est ignore"|||Sorry, I need to see that in English|||viola
"the safeguard cannot be carried out on this basis of data. This sub-task is ignored "
Google...yeah baby...|||Sorry, I need to see that in EnglishTo quote W.C. Fields "Go away kid, ya bother me!"
The nickel translation is something like: "That option can't be used for this database. It will be ignored."
-PatP|||Again, I'm working with lots of data. about 290,000,000 records. In the cleanup process backups of the data is most important. After each batch run I shrink the transaction log. With that amount of data soon the log will be as big as the data file. At least that's what I was running into. Please follow the instruction above.
I have error when i backup the transaction log of master and msdb database.
I think there is an error because the model of this database is simple.
can i modify the model and write full ?
I have another question,
I have a db with 1 db file of 11Go, i have to create secondary files or not.No, you can't change the Model database.
No, you don't need to add secondary files, but it might be a good idea.
-PatP|||Are you using the enterprise manager?|||Master database doesn't allow Differential or log backups.
Post the error message that u get while backing up the transaction log for msdb.
Howdy!|||From the tool list go to shrink database; File; change shrink to transaction log. before implentation. Go out to network and very the log size. Then go back to EM and shrink log. Again go for verifaction.
Live from Dodge City USA, Washington DC|||Yes i using entreprise manager
the error i get for msdb is the following :
"La sauvegarde ne peut tre effectue sur cette base de donnes. Cette sous-tche est ignore"|||Sorry, I need to see that in English|||viola
"the safeguard cannot be carried out on this basis of data. This sub-task is ignored "
Google...yeah baby...|||Sorry, I need to see that in EnglishTo quote W.C. Fields "Go away kid, ya bother me!"
The nickel translation is something like: "That option can't be used for this database. It will be ignored."
-PatP|||Again, I'm working with lots of data. about 290,000,000 records. In the cleanup process backups of the data is most important. After each batch run I shrink the transaction log. With that amount of data soon the log will be as big as the data file. At least that's what I was running into. Please follow the instruction above.
Subscribe to:
Posts (Atom)