Lowering priority: regarding

Showing posts with label regarding. Show all posts

Friday, March 30, 2012

Maintenance plan failing

i keep getting the following error in my Event Viewer regarding a maintnance
plan I have set up in MS SQL Server 2000:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'DB Maintenance Plan master, msdb, model''
(0x0D97085E32705247B590ADA245D3FE07) - Status: Failed - Invoked on:
2006-11-14 00:00:05 - Message: The job failed. The Job was invoked by
Schedule 76 (Schedule 1). The last step to run was step 1 (Step 1).
Any ideas about what I might be doing wrong?
--
John SchusterJohn Schuster wrote:
> i keep getting the following error in my Event Viewer regarding a maintnance
> plan I have set up in MS SQL Server 2000:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
> 'DB Maintenance Plan master, msdb, model''
> (0x0D97085E32705247B590ADA245D3FE07) - Status: Failed - Invoked on:
> 2006-11-14 00:00:05 - Message: The job failed. The Job was invoked by
> Schedule 76 (Schedule 1). The last step to run was step 1 (Step 1).
> Any ideas about what I might be doing wrong?
You can't do a transaction log backup on a database that is in Simple
recovery mode.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||> Any ideas about what I might be doing wrong?
Specify a report file for the maint plan. In there you will find the error messages that lead to the
job failure.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Schuster" <JohnSchuster@.discussions.microsoft.com> wrote in message
news:D4C6E493-E90D-45E6-80B2-3BC0170D8DEB@.microsoft.com...
>i keep getting the following error in my Event Viewer regarding a maintnance
> plan I have set up in MS SQL Server 2000:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
> 'DB Maintenance Plan master, msdb, model''
> (0x0D97085E32705247B590ADA245D3FE07) - Status: Failed - Invoked on:
> 2006-11-14 00:00:05 - Message: The job failed. The Job was invoked by
> Schedule 76 (Schedule 1). The last step to run was step 1 (Step 1).
> Any ideas about what I might be doing wrong?
> --
> John Schuster|||I set up a report and i get the following which doesn't tell me much:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'EPDDOCS3' as 'SEP\EPDDOCS3$' (trusted)
Starting maintenance plan 'DB Maintenance Plan master, msdb, model' on
11/14/2006 12:00:07 AM
Backup can not be performed on database 'master'. This sub task is ignored.
[1] Database model: Transaction Log Backup...
Destination: [X:\MSSQL\EPDdocs_BACKUP\model_tlog_200611140000.TRN]
** Execution Time: 0 hrs, 0 mins, 1 secs **
[2] Database model: Verifying Backup...
** Execution Time: 0 hrs, 0 mins, 1 secs **
Backup can not be performed on database 'msdb'. This sub task is ignored.
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan master, msdb, model' on
11/14/2006 12:00:08 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
--
John Schuster
"Tibor Karaszi" wrote:
> > Any ideas about what I might be doing wrong?
> Specify a report file for the maint plan. In there you will find the error messages that lead to the
> job failure.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "John Schuster" <JohnSchuster@.discussions.microsoft.com> wrote in message
> news:D4C6E493-E90D-45E6-80B2-3BC0170D8DEB@.microsoft.com...
> >i keep getting the following error in my Event Viewer regarding a maintnance
> > plan I have set up in MS SQL Server 2000:
> >
> > SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
> > 'DB Maintenance Plan master, msdb, model''
> > (0x0D97085E32705247B590ADA245D3FE07) - Status: Failed - Invoked on:
> > 2006-11-14 00:00:05 - Message: The job failed. The Job was invoked by
> > Schedule 76 (Schedule 1). The last step to run was step 1 (Step 1).
> >
> > Any ideas about what I might be doing wrong?
> > --
> > John Schuster
>
>|||Here's the problem:
> Backup can not be performed on database 'msdb'. This sub task is ignored.
You are trying to do a log backup on a database which is in simple recovery mode. No can do.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"John Schuster" <JohnSchuster@.discussions.microsoft.com> wrote in message
news:AC9FF4A5-0CF5-4661-A9F1-577320DB70A3@.microsoft.com...
>I set up a report and i get the following which doesn't tell me much:
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
> 'EPDDOCS3' as 'SEP\EPDDOCS3$' (trusted)
> Starting maintenance plan 'DB Maintenance Plan master, msdb, model' on
> 11/14/2006 12:00:07 AM
> Backup can not be performed on database 'master'. This sub task is ignored.
> [1] Database model: Transaction Log Backup...
> Destination: [X:\MSSQL\EPDdocs_BACKUP\model_tlog_200611140000.TRN]
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> [2] Database model: Verifying Backup...
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> Backup can not be performed on database 'msdb'. This sub task is ignored.
> Deleting old text reports... 0 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan master, msdb, model' on
> 11/14/2006 12:00:08 AM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
> --
> John Schuster
>
> "Tibor Karaszi" wrote:
>> > Any ideas about what I might be doing wrong?
>> Specify a report file for the maint plan. In there you will find the error messages that lead to
>> the
>> job failure.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "John Schuster" <JohnSchuster@.discussions.microsoft.com> wrote in message
>> news:D4C6E493-E90D-45E6-80B2-3BC0170D8DEB@.microsoft.com...
>> >i keep getting the following error in my Event Viewer regarding a maintnance
>> > plan I have set up in MS SQL Server 2000:
>> >
>> > SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
>> > 'DB Maintenance Plan master, msdb, model''
>> > (0x0D97085E32705247B590ADA245D3FE07) - Status: Failed - Invoked on:
>> > 2006-11-14 00:00:05 - Message: The job failed. The Job was invoked by
>> > Schedule 76 (Schedule 1). The last step to run was step 1 (Step 1).
>> >
>> > Any ideas about what I might be doing wrong?
>> > --
>> > John Schuster
>>|||Thank you for your help.
--
John Schuster
"Tibor Karaszi" wrote:
> Here's the problem:
> > Backup can not be performed on database 'msdb'. This sub task is ignored.
> You are trying to do a log backup on a database which is in simple recovery mode. No can do.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "John Schuster" <JohnSchuster@.discussions.microsoft.com> wrote in message
> news:AC9FF4A5-0CF5-4661-A9F1-577320DB70A3@.microsoft.com...
> >I set up a report and i get the following which doesn't tell me much:
> >
> > Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
> > 'EPDDOCS3' as 'SEP\EPDDOCS3$' (trusted)
> > Starting maintenance plan 'DB Maintenance Plan master, msdb, model' on
> > 11/14/2006 12:00:07 AM
> > Backup can not be performed on database 'master'. This sub task is ignored.
> >
> > [1] Database model: Transaction Log Backup...
> > Destination: [X:\MSSQL\EPDdocs_BACKUP\model_tlog_200611140000.TRN]
> >
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > [2] Database model: Verifying Backup...
> >
> > ** Execution Time: 0 hrs, 0 mins, 1 secs **
> >
> > Backup can not be performed on database 'msdb'. This sub task is ignored.
> >
> > Deleting old text reports... 0 file(s) deleted.
> >
> > End of maintenance plan 'DB Maintenance Plan master, msdb, model' on
> > 11/14/2006 12:00:08 AM
> > SQLMAINT.EXE Process Exit Code: 1 (Failed)
> > --
> > John Schuster
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> > Any ideas about what I might be doing wrong?
> >>
> >> Specify a report file for the maint plan. In there you will find the error messages that lead to
> >> the
> >> job failure.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "John Schuster" <JohnSchuster@.discussions.microsoft.com> wrote in message
> >> news:D4C6E493-E90D-45E6-80B2-3BC0170D8DEB@.microsoft.com...
> >> >i keep getting the following error in my Event Viewer regarding a maintnance
> >> > plan I have set up in MS SQL Server 2000:
> >> >
> >> > SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
> >> > 'DB Maintenance Plan master, msdb, model''
> >> > (0x0D97085E32705247B590ADA245D3FE07) - Status: Failed - Invoked on:
> >> > 2006-11-14 00:00:05 - Message: The job failed. The Job was invoked by
> >> > Schedule 76 (Schedule 1). The last step to run was step 1 (Step 1).
> >> >
> >> > Any ideas about what I might be doing wrong?
> >> > --
> >> > John Schuster
> >>
> >>
> >>
>

Monday, March 19, 2012

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Maintainence of Replication

Hi Dear...

I have some questions regarding replication in SQL Server 2005.

1. Is it neccessary to have same schema on each side i.e on subsicriber and on publisher?

2. Do replication helps me to replicate the changed schema (of published articals) to the subscribers?

3. If a UDT is defined on publisher and one of its dependent is selected for publication do i need to define the UDT on subscriber manually or it will automatically done for me?

4. pls anyone who can give me the detail known issues and their alternative solutions in regard of maintainence of Replication.

Regards

Mubashar Ahmad

1. Subscriber can have a either the full table, a portion of the table or not at all. You cannot replicate to a totally different schema though.

2. Yes it will replicate ALTER statements.

3. I think you have to do that manaully. However you can set a script to run before the snapshot to create it for you automatically.

4. I dont think anyone can give you that.

Martin

|||

For #3 you have options, see @.schema_option for sp_addarticle.

|||thanks both of you... i ll keep this in mind when i come back to replication.. at the moment i am on long vacations...

Maintain History

Hi All
I have a table that contains details regarding branch offices and as these
offices regularly change details such as the branch name and address I need
to always have the current details and also maintain a history of historical
details for each branch office. Initially I was think of having a duplicate
table with a datetime column to store when the last change was made and also
a column that contained the details of who changed the branch office details.
I was going to control this through the application but have identified that
there is any additional vendor application that also change details in this
table and the application can not be modified.
Is the best way to maintain a history of branch office details in this
scenario to create a trigger on the table and populate a duplicate table with
the details of the branch office as they where before being modified or is
there a better way to do this?
Thanks
- DavidHi David
There is a simple auditing example (E) in the Create Trigger topic in books
online. There may be an impact on the system if you implement these on all
your tables, in both the amount of storage used and time taken to make
changes. To reduce the performance degredation it is best to keep the trigger
as simple as you can , if any reconciliation is necessary then you can do
that during a quiet period of possibly offline.
Alternatively you can purchase a log reading program, you may want to log at
LogExplorer from Lumigent www.lumigent.com or LogPI which has been aquired
by Goldengate see www.logpi.com
John
"David" wrote:
> Hi All
> I have a table that contains details regarding branch offices and as these
> offices regularly change details such as the branch name and address I need
> to always have the current details and also maintain a history of historical
> details for each branch office. Initially I was think of having a duplicate
> table with a datetime column to store when the last change was made and also
> a column that contained the details of who changed the branch office details.
> I was going to control this through the application but have identified that
> there is any additional vendor application that also change details in this
> table and the application can not be modified.
> Is the best way to maintain a history of branch office details in this
> scenario to create a trigger on the table and populate a duplicate table with
> the details of the branch office as they where before being modified or is
> there a better way to do this?
> Thanks
> - David

Maintain History

Hi All
I have a table that contains details regarding branch offices and as these
offices regularly change details such as the branch name and address I need
to always have the current details and also maintain a history of historical
details for each branch office. Initially I was think of having a duplicate
table with a datetime column to store when the last change was made and also
a column that contained the details of who changed the branch office details
.
I was going to control this through the application but have identified that
there is any additional vendor application that also change details in this
table and the application can not be modified.
Is the best way to maintain a history of branch office details in this
scenario to create a trigger on the table and populate a duplicate table wit
h
the details of the branch office as they where before being modified or is
there a better way to do this?
Thanks
- DavidHi David
There is a simple auditing example (E) in the Create Trigger topic in books
online. There may be an impact on the system if you implement these on all
your tables, in both the amount of storage used and time taken to make
changes. To reduce the performance degredation it is best to keep the trigge
r
as simple as you can , if any reconciliation is necessary then you can do
that during a quiet period of possibly offline.
Alternatively you can purchase a log reading program, you may want to log at
LogExplorer from Lumigent www.lumigent.com or LogPI which has been aquired
by Goldengate see www.logpi.com
John
"David" wrote:

> Hi All
> I have a table that contains details regarding branch offices and as these
> offices regularly change details such as the branch name and address I nee
d
> to always have the current details and also maintain a history of historic
al
> details for each branch office. Initially I was think of having a duplica
te
> table with a datetime column to store when the last change was made and al
so
> a column that contained the details of who changed the branch office detai
ls.
> I was going to control this through the application but have identified t
hat
> there is any additional vendor application that also change details in thi
s
> table and the application can not be modified.
> Is the best way to maintain a history of branch office details in this
> scenario to create a trigger on the table and populate a duplicate table w
ith
> the details of the branch office as they where before being modified or is
> there a better way to do this?
> Thanks
> - David

Friday, March 30, 2012

Maintenance plan failing

Maintenance plan failing

Maintenance plan failing

Monday, March 19, 2012

Maintainence of Replication

Maintainence of Replication

Maintainence of Replication

Maintainence of Replication

Maintain History

Maintain History

Lowering priority

Blog Archive

About Me