Please help > Problem restoring database

We have 2 database on a production server running sql express 2005, the first one is 200mb and the other one is 1.3gig.

We make backup under sql management studio using option full.

When we try to recover database on another server the 200mb database restore perfectly, the 1.3 gig
always fail with the following message :

ADDITIONAL INFORMATION:

System.Data.SqlClient.SqlError: The file "database_name" failed to initialize correctly. Examine the error logs for more details. (Microsoft.SqlServer.Express.Smo)

We tried dbcc checkdb and everything seems alright.
I updated the statistics, no change.
I switched the recovery model from full to simple, no change.
I tried using "restore database from disk='' with norecovery, same error message

We tried stopping the production server then copying the file to the other server and attaching and it still fail with the following message :

An error occured when attaching the database(s). >

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\database_Data.MDF". Operating system error 8: "8(error not found)". (Microsoft SQL Server, Error: 5120)

We dont know what to try anymore, the goal is to be sure our backup are alright....

Please helppppp ! thank you.
sorry for my bad english...

Youhou !!!!!!! Finaly.

Ok, I uninstalled avg antivirus, then free my disk drive to have 10gig free.

restored my backup and it completed successfully !!!!

thank you for your help rmiaosql

Planning of log backup suggestions

Hello Guys,
I would like to overwrite the log file every two weeks.
The log file is backed up every hours every hours (append to the
device) and the full backup runs every day at 11 pm.
I would like to run a job that overwrite the log backup every two
weeks. What do you advice me to do? at which time is better?
I would like to overwrite the file every two weeks at 10 pm before of
the full backup.
any suggestion?
Ina
ina

> I would like to overwrite the log file every two weeks.
> The log file is backed up every hours every hours (append to the
> device) and the full backup runs every day at 11 pm.
BACKUP LOG... WITH INIT just after FULL BACKUP of the database
If you do Database20061101.bak as regular full backup , try to compare
GETDATE() -14 with '20061101' portion of .BAK file
Tools
1)CONVERT function
2)SUBSTRING/RIGHT/LEFT functions
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1163408898.605077.87490@.m73g2000cwd.googlegro ups.com...
> Hello Guys,
> I would like to overwrite the log file every two weeks.
> The log file is backed up every hours every hours (append to the
> device) and the full backup runs every day at 11 pm.
>
> I would like to run a job that overwrite the log backup every two
> weeks. What do you advice me to do? at which time is better?
> I would like to overwrite the file every two weeks at 10 pm before of
> the full backup.
> any suggestion?
> Ina
>
|||Thanks Uri,
I did not understand the this:
If you do Database20061101.bak as regular full backup , try to compare

> GETDATE() -14 with '20061101' portion of .BAK file
> Tools
> 1)CONVERT function
> 2)SUBSTRING/RIGHT/LEFT functions
Ina
Uri Dimant wrote:
[vbcol=seagreen]
> ina
>
> BACKUP LOG... WITH INIT just after FULL BACKUP of the database
> If you do Database20061101.bak as regular full backup , try to compare
> GETDATE() -14 with '20061101' portion of .BAK file
> Tools
> 1)CONVERT function
> 2)SUBSTRING/RIGHT/LEFT functions
>
>
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1163408898.605077.87490@.m73g2000cwd.googlegro ups.com...
|||ina
It is how you identify your backup file
DECLARE @.FileName AS VARCHAR(255)
DECLARE @.Date AS VARCHAR(20)
SET @.Date =CONVERT(VARCHAR(10),GETDATE(),112)
SELECT @.FileName = 'C:\dbname' + @.Date+'.bak'
BACKUP DATABASE dbname TO DISK = @.FileName
Now you have to compare , whether the .BAK file is two weeks old and if it
is you just perform BACKUP LOG ...WITH INIT
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1163414330.502761.160300@.h48g2000cwc.googlegr oups.com...
> Thanks Uri,
> I did not understand the this:
> If you do Database20061101.bak as regular full backup , try to compare
>
> Ina
>
> Uri Dimant wrote:
>
|||Ah ok thanks did not know So I can do a job that everyday test this
validation and if it true a overwrite the device.
Ina
Uri Dimant wrote:
[vbcol=seagreen]
> ina
> It is how you identify your backup file
> DECLARE @.FileName AS VARCHAR(255)
> DECLARE @.Date AS VARCHAR(20)
> SET @.Date =CONVERT(VARCHAR(10),GETDATE(),112)
> SELECT @.FileName = 'C:\dbname' + @.Date+'.bak'
> BACKUP DATABASE dbname TO DISK = @.FileName
>
> Now you have to compare , whether the .BAK file is two weeks old and if it
> is you just perform BACKUP LOG ...WITH INIT
>
>
>
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1163414330.502761.160300@.h48g2000cwc.googlegr oups.com...

Planning of log backup suggestions

Hello Guys,
I would like to overwrite the log file every two weeks.
The log file is backed up every hours every hours (append to the
device) and the full backup runs every day at 11 pm.
I would like to run a job that overwrite the log backup every two
weeks. What do you advice me to do? at which time is better?
I would like to overwrite the file every two weeks at 10 pm before of
the full backup.
any suggestion?
Inaina
> I would like to overwrite the log file every two weeks.
> The log file is backed up every hours every hours (append to the
> device) and the full backup runs every day at 11 pm.
BACKUP LOG... WITH INIT just after FULL BACKUP of the database
If you do Database20061101.bak as regular full backup , try to compare
GETDATE() -14 with '20061101' portion of .BAK file
Tools
1)CONVERT function
2)SUBSTRING/RIGHT/LEFT functions
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1163408898.605077.87490@.m73g2000cwd.googlegroups.com...
> Hello Guys,
> I would like to overwrite the log file every two weeks.
> The log file is backed up every hours every hours (append to the
> device) and the full backup runs every day at 11 pm.
>
> I would like to run a job that overwrite the log backup every two
> weeks. What do you advice me to do? at which time is better?
> I would like to overwrite the file every two weeks at 10 pm before of
> the full backup.
> any suggestion?
> Ina
>|||Thanks Uri,
I did not understand the this:
If you do Database20061101.bak as regular full backup , try to compare
> GETDATE() -14 with '20061101' portion of .BAK file
> Tools
> 1)CONVERT function
> 2)SUBSTRING/RIGHT/LEFT functions
Ina
Uri Dimant wrote:
> ina
> > I would like to overwrite the log file every two weeks.
> >
> > The log file is backed up every hours every hours (append to the
> > device) and the full backup runs every day at 11 pm.
>
> BACKUP LOG... WITH INIT just after FULL BACKUP of the database
> If you do Database20061101.bak as regular full backup , try to compare
> GETDATE() -14 with '20061101' portion of .BAK file
> Tools
> 1)CONVERT function
> 2)SUBSTRING/RIGHT/LEFT functions
>
>
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1163408898.605077.87490@.m73g2000cwd.googlegroups.com...
> > Hello Guys,
> >
> > I would like to overwrite the log file every two weeks.
> >
> > The log file is backed up every hours every hours (append to the
> > device) and the full backup runs every day at 11 pm.
> >
> >
> > I would like to run a job that overwrite the log backup every two
> > weeks. What do you advice me to do? at which time is better?
> >
> > I would like to overwrite the file every two weeks at 10 pm before of
> > the full backup.
> >
> > any suggestion?
> >
> > Ina
> >|||ina
It is how you identify your backup file
DECLARE @.FileName AS VARCHAR(255)
DECLARE @.Date AS VARCHAR(20)
SET @.Date =CONVERT(VARCHAR(10),GETDATE(),112)
SELECT @.FileName = 'C:\dbname' + @.Date+'.bak'
BACKUP DATABASE dbname TO DISK = @.FileName
Now you have to compare , whether the .BAK file is two weeks old and if it
is you just perform BACKUP LOG ...WITH INIT
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1163414330.502761.160300@.h48g2000cwc.googlegroups.com...
> Thanks Uri,
> I did not understand the this:
> If you do Database20061101.bak as regular full backup , try to compare
>> GETDATE() -14 with '20061101' portion of .BAK file
>> Tools
>> 1)CONVERT function
>> 2)SUBSTRING/RIGHT/LEFT functions
> Ina
>
> Uri Dimant wrote:
>> ina
>> > I would like to overwrite the log file every two weeks.
>> >
>> > The log file is backed up every hours every hours (append to the
>> > device) and the full backup runs every day at 11 pm.
>>
>> BACKUP LOG... WITH INIT just after FULL BACKUP of the database
>> If you do Database20061101.bak as regular full backup , try to compare
>> GETDATE() -14 with '20061101' portion of .BAK file
>> Tools
>> 1)CONVERT function
>> 2)SUBSTRING/RIGHT/LEFT functions
>>
>>
>>
>> "ina" <roberta.inalbon@.gmail.com> wrote in message
>> news:1163408898.605077.87490@.m73g2000cwd.googlegroups.com...
>> > Hello Guys,
>> >
>> > I would like to overwrite the log file every two weeks.
>> >
>> > The log file is backed up every hours every hours (append to the
>> > device) and the full backup runs every day at 11 pm.
>> >
>> >
>> > I would like to run a job that overwrite the log backup every two
>> > weeks. What do you advice me to do? at which time is better?
>> >
>> > I would like to overwrite the file every two weeks at 10 pm before of
>> > the full backup.
>> >
>> > any suggestion?
>> >
>> > Ina
>> >
>|||Ah ok thanks did not know So I can do a job that everyday test this
validation and if it true a overwrite the device.
Ina
Uri Dimant wrote:
> ina
> It is how you identify your backup file
> DECLARE @.FileName AS VARCHAR(255)
> DECLARE @.Date AS VARCHAR(20)
> SET @.Date =CONVERT(VARCHAR(10),GETDATE(),112)
> SELECT @.FileName = 'C:\dbname' + @.Date+'.bak'
> BACKUP DATABASE dbname TO DISK = @.FileName
>
> Now you have to compare , whether the .BAK file is two weeks old and if it
> is you just perform BACKUP LOG ...WITH INIT
>
>
>
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1163414330.502761.160300@.h48g2000cwc.googlegroups.com...
> > Thanks Uri,
> >
> > I did not understand the this:
> >
> > If you do Database20061101.bak as regular full backup , try to compare
> >
> >> GETDATE() -14 with '20061101' portion of .BAK file
> >>
> >> Tools
> >>
> >> 1)CONVERT function
> >> 2)SUBSTRING/RIGHT/LEFT functions
> >
> > Ina
> >
> >
> > Uri Dimant wrote:
> >
> >> ina
> >>
> >> > I would like to overwrite the log file every two weeks.
> >> >
> >> > The log file is backed up every hours every hours (append to the
> >> > device) and the full backup runs every day at 11 pm.
> >>
> >>
> >> BACKUP LOG... WITH INIT just after FULL BACKUP of the database
> >>
> >> If you do Database20061101.bak as regular full backup , try to compare
> >> GETDATE() -14 with '20061101' portion of .BAK file
> >>
> >> Tools
> >>
> >> 1)CONVERT function
> >> 2)SUBSTRING/RIGHT/LEFT functions
> >>
> >>
> >>
> >>
> >>
> >>
> >> "ina" <roberta.inalbon@.gmail.com> wrote in message
> >> news:1163408898.605077.87490@.m73g2000cwd.googlegroups.com...
> >> > Hello Guys,
> >> >
> >> > I would like to overwrite the log file every two weeks.
> >> >
> >> > The log file is backed up every hours every hours (append to the
> >> > device) and the full backup runs every day at 11 pm.
> >> >
> >> >
> >> > I would like to run a job that overwrite the log backup every two
> >> > weeks. What do you advice me to do? at which time is better?
> >> >
> >> > I would like to overwrite the file every two weeks at 10 pm before of
> >> > the full backup.
> >> >
> >> > any suggestion?
> >> >
> >> > Ina
> >> >
> >

Planning of log backup suggestions

Hello Guys,
I would like to overwrite the log file every two weeks.
The log file is backed up every hours every hours (append to the
device) and the full backup runs every day at 11 pm.
I would like to run a job that overwrite the log backup every two
weeks. What do you advice me to do? at which time is better?
I would like to overwrite the file every two weeks at 10 pm before of
the full backup.
any suggestion?
Inaina

> I would like to overwrite the log file every two weeks.
> The log file is backed up every hours every hours (append to the
> device) and the full backup runs every day at 11 pm.
BACKUP LOG... WITH INIT just after FULL BACKUP of the database
If you do Database20061101.bak as regular full backup , try to compare
GETDATE() -14 with '20061101' portion of .BAK file
Tools
1)CONVERT function
2)SUBSTRING/RIGHT/LEFT functions
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1163408898.605077.87490@.m73g2000cwd.googlegroups.com...
> Hello Guys,
> I would like to overwrite the log file every two weeks.
> The log file is backed up every hours every hours (append to the
> device) and the full backup runs every day at 11 pm.
>
> I would like to run a job that overwrite the log backup every two
> weeks. What do you advice me to do? at which time is better?
> I would like to overwrite the file every two weeks at 10 pm before of
> the full backup.
> any suggestion?
> Ina
>|||Thanks Uri,
I did not understand the this:
If you do Database20061101.bak as regular full backup , try to compare

> GETDATE() -14 with '20061101' portion of .BAK file
> Tools
> 1)CONVERT function
> 2)SUBSTRING/RIGHT/LEFT functions
Ina
Uri Dimant wrote:
[vbcol=seagreen]
> ina
>
>
> BACKUP LOG... WITH INIT just after FULL BACKUP of the database
> If you do Database20061101.bak as regular full backup , try to compare
> GETDATE() -14 with '20061101' portion of .BAK file
> Tools
> 1)CONVERT function
> 2)SUBSTRING/RIGHT/LEFT functions
>
>
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1163408898.605077.87490@.m73g2000cwd.googlegroups.com...|||ina
It is how you identify your backup file
DECLARE @.FileName AS VARCHAR(255)
DECLARE @.Date AS VARCHAR(20)
SET @.Date =CONVERT(VARCHAR(10),GETDATE(),112)
SELECT @.FileName = 'C:\dbname' + @.Date+'.bak'
BACKUP DATABASE dbname TO DISK = @.FileName
Now you have to compare , whether the .BAK file is two weeks old and if it
is you just perform BACKUP LOG ...WITH INIT
"ina" <roberta.inalbon@.gmail.com> wrote in message
news:1163414330.502761.160300@.h48g2000cwc.googlegroups.com...
> Thanks Uri,
> I did not understand the this:
> If you do Database20061101.bak as regular full backup , try to compare
>
> Ina
>
> Uri Dimant wrote:
>
>|||Ah ok thanks did not know So I can do a job that everyday test this
validation and if it true a overwrite the device.
Ina
Uri Dimant wrote:
[vbcol=seagreen]
> ina
> It is how you identify your backup file
> DECLARE @.FileName AS VARCHAR(255)
> DECLARE @.Date AS VARCHAR(20)
> SET @.Date =CONVERT(VARCHAR(10),GETDATE(),112)
> SELECT @.FileName = 'C:\dbname' + @.Date+'.bak'
> BACKUP DATABASE dbname TO DISK = @.FileName
>
> Now you have to compare , whether the .BAK file is two weeks old and if i
t
> is you just perform BACKUP LOG ...WITH INIT
>
>
>
>
> "ina" <roberta.inalbon@.gmail.com> wrote in message
> news:1163414330.502761.160300@.h48g2000cwc.googlegroups.com...

Plan Maintenance will not execute

My plan Maintenance to Optimize, TRN Backup and Reporting
has been running for several months. A few days ago, I
started getting the following in "View Job History":
"Executed as user: domain\Administrator. sqlmaint.exe
failed. [SQLSTATE 42000] (Error 22029). The step failed."
There is no log file created, even though I requested one,
which leads me to believe the Job never actually started.
The Windows 2000 Applications Log has the following:
"SQL Server Scheduled Job 'Optimizations Job for DB
Maintenance Plan 'Test 1''
(0x529723559D047845AB998AFF9BDA397F) - Status: Failed -
Invoked on: 2004-07-14 22:30:00 - Message: The job
failed. The Job was invoked by Schedule 42 (Schedule 1).
The last step to run was step 1 (Step 1)."
When I try and run the command in Query Analyzer, I get
the following:
"Server: Msg 22029, Level 16, State 1, Line 0
sqlmaint.exe failed."
The recovery model is "Bulk-Logged"
Does anyone have any Idea what has gone wrong in this
maintenance Plan?Hi,
By any chance did you changed the recovery model for a database to SIMPLE
and then turned back to BULK_LOGGED. In this
case you have to do a FULL database backup for that database.
command:
--
BACKUP database <dbname> to disk='d:\backup\dbname.bak' with init
Thanks
Hari
MCDBA
"Ken Bitner" <anonymous@.discussions.microsoft.com> wrote in message
news:2d53601c46a17$38dd0f20$a501280a@.phx
.gbl...
> My plan Maintenance to Optimize, TRN Backup and Reporting
> has been running for several months. A few days ago, I
> started getting the following in "View Job History":
> "Executed as user: domain\Administrator. sqlmaint.exe
> failed. [SQLSTATE 42000] (Error 22029). The step failed."
> There is no log file created, even though I requested one,
> which leads me to believe the Job never actually started.
> The Windows 2000 Applications Log has the following:
> "SQL Server Scheduled Job 'Optimizations Job for DB
> Maintenance Plan 'Test 1''
> (0x529723559D047845AB998AFF9BDA397F) - Status: Failed -
> Invoked on: 2004-07-14 22:30:00 - Message: The job
> failed. The Job was invoked by Schedule 42 (Schedule 1).
> The last step to run was step 1 (Step 1)."
> When I try and run the command in Query Analyzer, I get
> the following:
> "Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed."
> The recovery model is "Bulk-Logged"
> Does anyone have any Idea what has gone wrong in this
> maintenance Plan?
>
>|||No. The Recovery Model has always been "Bulk-Logged".
Also, I have take a full backup every day via the same
command you sent me.

>--Original Message--
>Hi,
>By any chance did you changed the recovery model for a
database to SIMPLE
>and then turned back to BULK_LOGGED. In this
>case you have to do a FULL database backup for that
database.
>command:
>--
>BACKUP database <dbname> to disk='d:\backup\dbname.bak'
with init
>
>--
>Thanks
>Hari
>MCDBA
>
>"Ken Bitner" <anonymous@.discussions.microsoft.com> wrote
in message
> news:2d53601c46a17$38dd0f20$a501280a@.phx
.gbl...
Reporting[vbcol=seagreen]
failed."[vbcol=seagreen]
one,[vbcol=seagreen]
started.[vbcol=seagreen]
1).[vbcol=seagreen]
>
>.
>

Plan Maintenance will not execute

My plan Maintenance to Optimize, TRN Backup and Reporting
has been running for several months. A few days ago, I
started getting the following in "View Job History":
"Executed as user: domain\Administrator. sqlmaint.exe
failed. [SQLSTATE 42000] (Error 22029). The step failed."
There is no log file created, even though I requested one,
which leads me to believe the Job never actually started.
The Windows 2000 Applications Log has the following:
"SQL Server Scheduled Job 'Optimizations Job for DB
Maintenance Plan 'Test 1''
(0x529723559D047845AB998AFF9BDA397F) - Status: Failed -
Invoked on: 2004-07-14 22:30:00 - Message: The job
failed. The Job was invoked by Schedule 42 (Schedule 1).
The last step to run was step 1 (Step 1)."
When I try and run the command in Query Analyzer, I get
the following:
"Server: Msg 22029, Level 16, State 1, Line 0
sqlmaint.exe failed."
The recovery model is "Bulk-Logged"
Does anyone have any Idea what has gone wrong in this
maintenance Plan?
Hi,
By any chance did you changed the recovery model for a database to SIMPLE
and then turned back to BULK_LOGGED. In this
case you have to do a FULL database backup for that database.
command:
BACKUP database <dbname> to disk='d:\backup\dbname.bak' with init
Thanks
Hari
MCDBA
"Ken Bitner" <anonymous@.discussions.microsoft.com> wrote in message
news:2d53601c46a17$38dd0f20$a501280a@.phx.gbl...
> My plan Maintenance to Optimize, TRN Backup and Reporting
> has been running for several months. A few days ago, I
> started getting the following in "View Job History":
> "Executed as user: domain\Administrator. sqlmaint.exe
> failed. [SQLSTATE 42000] (Error 22029). The step failed."
> There is no log file created, even though I requested one,
> which leads me to believe the Job never actually started.
> The Windows 2000 Applications Log has the following:
> "SQL Server Scheduled Job 'Optimizations Job for DB
> Maintenance Plan 'Test 1''
> (0x529723559D047845AB998AFF9BDA397F) - Status: Failed -
> Invoked on: 2004-07-14 22:30:00 - Message: The job
> failed. The Job was invoked by Schedule 42 (Schedule 1).
> The last step to run was step 1 (Step 1)."
> When I try and run the command in Query Analyzer, I get
> the following:
> "Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed."
> The recovery model is "Bulk-Logged"
> Does anyone have any Idea what has gone wrong in this
> maintenance Plan?
>
>
|||No. The Recovery Model has always been "Bulk-Logged".
Also, I have take a full backup every day via the same
command you sent me.

>--Original Message--
>Hi,
>By any chance did you changed the recovery model for a
database to SIMPLE
>and then turned back to BULK_LOGGED. In this
>case you have to do a FULL database backup for that
database.
>command:
>--
>BACKUP database <dbname> to disk='d:\backup\dbname.bak'
with init
>
>--
>Thanks
>Hari
>MCDBA
>
>"Ken Bitner" <anonymous@.discussions.microsoft.com> wrote
in message[vbcol=seagreen]
>news:2d53601c46a17$38dd0f20$a501280a@.phx.gbl...
Reporting[vbcol=seagreen]
failed."[vbcol=seagreen]
one,[vbcol=seagreen]
started.[vbcol=seagreen]
1).
>
>.
>

Plan Maintenance will not execute

My plan Maintenance to Optimize, TRN Backup and Reporting
has been running for several months. A few days ago, I
started getting the following in "View Job History":
"Executed as user: domain\Administrator. sqlmaint.exe
failed. [SQLSTATE 42000] (Error 22029). The step failed."
There is no log file created, even though I requested one,
which leads me to believe the Job never actually started.
The Windows 2000 Applications Log has the following:
"SQL Server Scheduled Job 'Optimizations Job for DB
Maintenance Plan 'Test 1''
(0x529723559D047845AB998AFF9BDA397F) - Status: Failed -
Invoked on: 2004-07-14 22:30:00 - Message: The job
failed. The Job was invoked by Schedule 42 (Schedule 1).
The last step to run was step 1 (Step 1)."
When I try and run the command in Query Analyzer, I get
the following:
"Server: Msg 22029, Level 16, State 1, Line 0
sqlmaint.exe failed."
The recovery model is "Bulk-Logged"
Does anyone have any Idea what has gone wrong in this
maintenance Plan?Hi,
By any chance did you changed the recovery model for a database to SIMPLE
and then turned back to BULK_LOGGED. In this
case you have to do a FULL database backup for that database.
command:
--
BACKUP database <dbname> to disk='d:\backup\dbname.bak' with init
Thanks
Hari
MCDBA
"Ken Bitner" <anonymous@.discussions.microsoft.com> wrote in message
news:2d53601c46a17$38dd0f20$a501280a@.phx.gbl...
> My plan Maintenance to Optimize, TRN Backup and Reporting
> has been running for several months. A few days ago, I
> started getting the following in "View Job History":
> "Executed as user: domain\Administrator. sqlmaint.exe
> failed. [SQLSTATE 42000] (Error 22029). The step failed."
> There is no log file created, even though I requested one,
> which leads me to believe the Job never actually started.
> The Windows 2000 Applications Log has the following:
> "SQL Server Scheduled Job 'Optimizations Job for DB
> Maintenance Plan 'Test 1''
> (0x529723559D047845AB998AFF9BDA397F) - Status: Failed -
> Invoked on: 2004-07-14 22:30:00 - Message: The job
> failed. The Job was invoked by Schedule 42 (Schedule 1).
> The last step to run was step 1 (Step 1)."
> When I try and run the command in Query Analyzer, I get
> the following:
> "Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed."
> The recovery model is "Bulk-Logged"
> Does anyone have any Idea what has gone wrong in this
> maintenance Plan?
>
>|||No. The Recovery Model has always been "Bulk-Logged".
Also, I have take a full backup every day via the same
command you sent me.
>--Original Message--
>Hi,
>By any chance did you changed the recovery model for a
database to SIMPLE
>and then turned back to BULK_LOGGED. In this
>case you have to do a FULL database backup for that
database.
>command:
>--
>BACKUP database <dbname> to disk='d:\backup\dbname.bak'
with init
>
>--
>Thanks
>Hari
>MCDBA
>
>"Ken Bitner" <anonymous@.discussions.microsoft.com> wrote
in message
>news:2d53601c46a17$38dd0f20$a501280a@.phx.gbl...
>> My plan Maintenance to Optimize, TRN Backup and
Reporting
>> has been running for several months. A few days ago, I
>> started getting the following in "View Job History":
>> "Executed as user: domain\Administrator. sqlmaint.exe
>> failed. [SQLSTATE 42000] (Error 22029). The step
failed."
>> There is no log file created, even though I requested
one,
>> which leads me to believe the Job never actually
started.
>> The Windows 2000 Applications Log has the following:
>> "SQL Server Scheduled Job 'Optimizations Job for DB
>> Maintenance Plan 'Test 1''
>> (0x529723559D047845AB998AFF9BDA397F) - Status: Failed -
>> Invoked on: 2004-07-14 22:30:00 - Message: The job
>> failed. The Job was invoked by Schedule 42 (Schedule
1).
>> The last step to run was step 1 (Step 1)."
>> When I try and run the command in Query Analyzer, I get
>> the following:
>> "Server: Msg 22029, Level 16, State 1, Line 0
>> sqlmaint.exe failed."
>> The recovery model is "Bulk-Logged"
>> Does anyone have any Idea what has gone wrong in this
>> maintenance Plan?
>>
>
>.
>

plan for box upgrade

sql2k sp3
Im going to be moving sql from one box to a newer one
with better hardware today. This is my plan:
Restore a backup of Master and MSDB onto the new box.
Detach and attach the user db's.
Ive used detach and attach but never in this scenario.
Does anyone see a problem with this?
TIA, ChrisYour plan is perfect, only thing is that the restored
master database will still have entries for user
databases, even if they don't exist on new server yet. I
believe you can get rid of them by issuing drop database
command.
Then start attachig user databases, and then msdb.
hth.
>--Original Message--
>sql2k sp3
>Im going to be moving sql from one box to a newer one
>with better hardware today. This is my plan:
>Restore a backup of Master and MSDB onto the new box.
>Detach and attach the user db's.
>Ive used detach and attach but never in this scenario.
>Does anyone see a problem with this?
>TIA, Chris
>
>.
>|||My plan wasnt to detach and attach msdb at all. It was to
backup/ restore it. Will this still work?
>--Original Message--
>Your plan is perfect, only thing is that the restored
>master database will still have entries for user
>databases, even if they don't exist on new server yet. I
>believe you can get rid of them by issuing drop database
>command.
>Then start attachig user databases, and then msdb.
>
>hth.
>>--Original Message--
>>sql2k sp3
>>Im going to be moving sql from one box to a newer one
>>with better hardware today. This is my plan:
>>Restore a backup of Master and MSDB onto the new box.
>>Detach and attach the user db's.
>>Ive used detach and attach but never in this scenario.
>>Does anyone see a problem with this?
>>TIA, Chris
>>
>>.
>.
>|||you can backup/restore or attach/detach msdb database. or
just rename new mdf and ldf files for msdb on new server
(just for backup) and then copy original mdf/ldf files in
their place when the sql server is not running.
You can do same for master database as well, if you don't
want to use backup/restore.
hth.
>--Original Message--
>My plan wasnt to detach and attach msdb at all. It was to
>backup/ restore it. Will this still work?
>
>>--Original Message--
>>Your plan is perfect, only thing is that the restored
>>master database will still have entries for user
>>databases, even if they don't exist on new server yet. I
>>believe you can get rid of them by issuing drop database
>>command.
>>Then start attachig user databases, and then msdb.
>>
>>hth.
>>--Original Message--
>>sql2k sp3
>>Im going to be moving sql from one box to a newer one
>>with better hardware today. This is my plan:
>>Restore a backup of Master and MSDB onto the new box.
>>Detach and attach the user db's.
>>Ive used detach and attach but never in this scenario.
>>Does anyone see a problem with this?
>>TIA, Chris
>>
>>.
>>.
>.
>