This might be a stupid questions but,
Can you have a MSDE 2000 and SQL server
standard/enterprise on the same machine?
If not, can you have to instances of SQL databse with
different passwords for the 'sa' account in the respective
instances.
Many thanks
NicYou can have up to 16 instances of any edition of SQL Server 2000 (including
MSDE 2000) on a single computer.
sa is just one login that can be a member of the sysadmin fixed server role.
Any login in the sysadmin fixed server role has sys admin priviledges for
that instance of SQL Server. This would extend to any database for the
instance.
--
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Friday, March 30, 2012
Friday, March 9, 2012
MSDE - Job Scheduling and Stored Procedures
Can MSDE run stored procedures? Does MSDE have the same job scheduling features that SQL Standard and Enterprise Edition have?
SR
Yes and yes.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SR" <mv2k_2003-news@.yahoo.com> wrote in message news:ALq0d.13990$QJ3.9851@.newssvr21.news.prodigy.c om...
Can MSDE run stored procedures? Does MSDE have the same job scheduling features that SQL Standard and Enterprise Edition have?
SR
|||yes and no.
The SQL Express does not have job scheduler on board.
regards
bav
SR
Yes and yes.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SR" <mv2k_2003-news@.yahoo.com> wrote in message news:ALq0d.13990$QJ3.9851@.newssvr21.news.prodigy.c om...
Can MSDE run stored procedures? Does MSDE have the same job scheduling features that SQL Standard and Enterprise Edition have?
SR
|||yes and no.
The SQL Express does not have job scheduler on board.
regards
bav
Wednesday, March 7, 2012
msdb Unavailable
I work on a SQL 2000 Standard server that is part of our SBS package. Two days ago we ran a set of MS updates on the server and the residual symptom is that DTS packages, the Import or Export wizard all will not run. The Sql Server Agent service runs under the local system account, however that was true prior to the updates.
The error when attempting to run an import is that the OLEDB connection object is not available. The error occurs when trying to use the Access driver or a DSN. Further investigation indicates that msdb could not be contacted.
Does anyone have an idea as to what might cause this and a workaround?
Thanks,
misdeanI would perform an integrity check (DBCC CHECKDB) of the MSDE database, to se if it is corrupt. It might be because it's late night here, but that's the only reason I could think of now.|||I will give it a try. Somehow, I believe is is related to the MS updates applied the other day. I will run DBCC on it in the AM and post the results.
Thanks,
Keith
The error when attempting to run an import is that the OLEDB connection object is not available. The error occurs when trying to use the Access driver or a DSN. Further investigation indicates that msdb could not be contacted.
Does anyone have an idea as to what might cause this and a workaround?
Thanks,
misdeanI would perform an integrity check (DBCC CHECKDB) of the MSDE database, to se if it is corrupt. It might be because it's late night here, but that's the only reason I could think of now.|||I will give it a try. Somehow, I believe is is related to the MS updates applied the other day. I will run DBCC on it in the AM and post the results.
Thanks,
Keith
Monday, February 20, 2012
MSDB database
I have under SQL Server 2000 Standard Version with SP3a on Windows 2000 SP4
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?
> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:
> option
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recove
ry
models are supported for model, msdb and distribution." since full recovery
on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databas
es.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will
try
to backup the logs for db's in simple recovery and then generate errors. i'
ve
written a script that skips simple recovery db's for the log backups, why ca
n't
microsoft implement it in the dbmp jobs?
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?
> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:
> option
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recove
ry
models are supported for model, msdb and distribution." since full recovery
on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databas
es.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will
try
to backup the logs for db's in simple recovery and then generate errors. i'
ve
written a script that skips simple recovery db's for the log backups, why ca
n't
microsoft implement it in the dbmp jobs?
MSDB database
I have under SQL Server 2000 Standard Version with SP3a on Windows 2000 SP4
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?
> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
--
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:
> > anyone has any ideas why/what process, etc. would reset the recovery
> option
> > from FULL to SIMPLE?
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recovery
models are supported for model, msdb and distribution." since full recovery on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databases.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will try
to backup the logs for db's in simple recovery and then generate errors. i've
written a script that skips simple recovery db's for the log backups, why can't
microsoft implement it in the dbmp jobs?
a Database Maintenance plan to backup transaction logs of all databases
hourly.
This job has been frequently failing, and the reason is that on the MSDB
database, the Recovery option has for some mysterious reason frequently been
reset from FULL to SIMPLE, and in order to get transaction logs backing up,
it needs to be set to FULL.
anyone has any ideas why/what process, etc. would reset the recovery option
from FULL to SIMPLE?> I have under SQL Server 2000 Standard Version with SP3a on Windows 2000
SP4
> a Database Maintenance plan to backup transaction logs of all databases
> hourly.
Backing up the transaction logs from all databases seems like overkill.
What is the point, e.g. for tempdb?
> anyone has any ideas why/what process, etc. would reset the recovery
option
> from FULL to SIMPLE?
This is the way SQL Server works.
http://www.support.microsoft.com/?id=257856
If you really want to back up msdb every hour, then you can make a task in
your job to temporarily set the recovery model to FULL. However this won't
accomplish much as the transaction logs won't be complete (and maybe not
even usable, depending on how you plan to use them).
If you want the behavior to be different, you can let Microsoft know how you
feel: sqlwish@.microsoft.com
--
Aaron Bertrand
SQL Server MVP|||Aaron Bertrand - MVP wrote:
> > anyone has any ideas why/what process, etc. would reset the recovery
> option
> > from FULL to SIMPLE?
> This is the way SQL Server works.
> http://www.support.microsoft.com/?id=257856
>
that link is interesting. sort of contradicts the line from BOL "All recovery
models are supported for model, msdb and distribution." since full recovery on
msdb only works until sqlagent is restarted.
i always prefer to have a dbmp for user databases and one for system databases.
in the system one, i don't back up transaction logs.
i think it's sort of goofy that the transaction log backup from a dbmp will try
to backup the logs for db's in simple recovery and then generate errors. i've
written a script that skips simple recovery db's for the log backups, why can't
microsoft implement it in the dbmp jobs?
MSDB and PUBS Databases
We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Server.
We setup a SQL backup to run under SQL. We got the messages in the report.
It said "backup cannot be performed on database 'msdb'. This subtask is
ignored." and "Backup cannot be performed on database 'pubs'. This subtask
is ignored". Is it necessary to backup msdb and pubs databases? Thanks.Hi Diane
My guess is that this error is occurring when you try to back up the
transaction log of these databases, as they are in simple mode and the log
cannot be backed up.
Pubs is a sample database used in the documentation examples, and can be
easily rebuilt. It should never need to be backed up at all. MSDB should be
backed up so you can restore information about your tasks, jobs, alerts and
backup history. But you may be backing up the full database already and it
may only be the log backup that is failing.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Server. We setup a SQL backup to run under SQL. We got the messages in
> the report. It said "backup cannot be performed on database 'msdb'. This
> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
> This subtask is ignored". Is it necessary to backup msdb and pubs
> databases? Thanks.
>|||MSDB stores all you job as well as replication information, so backin
this up can save you lot of time in a disastery case. Pubs is jut a
sample database, if you want to you can leave this out, as you can
download the creation script somewhere on the MSDN space of microsoft.
HTH, Jens Suessmeyer.|||Thank you very much, Kalen for your prompt response.
Under Database Maintenance, a complete backup runs once a week and
transaction backup runs everyday. You are right. The error message comes
from the transaction log history. Do you suggest that I ignore the error
messages since I have a complete backup runs every week? I will uncheck the
backup for the PUBS database.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eyN$1mJOGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Diane
> My guess is that this error is occurring when you try to back up the
> transaction log of these databases, as they are in simple mode and the log
> cannot be backed up.
> Pubs is a sample database used in the documentation examples, and can be
> easily rebuilt. It should never need to be backed up at all. MSDB should
> be backed up so you can restore information about your tasks, jobs, alerts
> and backup history. But you may be backing up the full database already
> and it may only be the log backup that is failing.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
>
>|||Thanks for your prompt response, Jens. I just unchecked the backup for the
PUBS database. Thanks.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1140713647.322715.266680@.g47g2000cwa.googlegroups.com...
> MSDB stores all you job as well as replication information, so backin
> this up can save you lot of time in a disastery case. Pubs is jut a
> sample database, if you want to you can leave this out, as you can
> download the creation script somewhere on the MSDN space of microsoft.
> HTH, Jens Suessmeyer.
>
We setup a SQL backup to run under SQL. We got the messages in the report.
It said "backup cannot be performed on database 'msdb'. This subtask is
ignored." and "Backup cannot be performed on database 'pubs'. This subtask
is ignored". Is it necessary to backup msdb and pubs databases? Thanks.Hi Diane
My guess is that this error is occurring when you try to back up the
transaction log of these databases, as they are in simple mode and the log
cannot be backed up.
Pubs is a sample database used in the documentation examples, and can be
easily rebuilt. It should never need to be backed up at all. MSDB should be
backed up so you can restore information about your tasks, jobs, alerts and
backup history. But you may be backing up the full database already and it
may only be the log backup that is failing.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Server. We setup a SQL backup to run under SQL. We got the messages in
> the report. It said "backup cannot be performed on database 'msdb'. This
> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
> This subtask is ignored". Is it necessary to backup msdb and pubs
> databases? Thanks.
>|||MSDB stores all you job as well as replication information, so backin
this up can save you lot of time in a disastery case. Pubs is jut a
sample database, if you want to you can leave this out, as you can
download the creation script somewhere on the MSDN space of microsoft.
HTH, Jens Suessmeyer.|||Thank you very much, Kalen for your prompt response.
Under Database Maintenance, a complete backup runs once a week and
transaction backup runs everyday. You are right. The error message comes
from the transaction log history. Do you suggest that I ignore the error
messages since I have a complete backup runs every week? I will uncheck the
backup for the PUBS database.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eyN$1mJOGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Diane
> My guess is that this error is occurring when you try to back up the
> transaction log of these databases, as they are in simple mode and the log
> cannot be backed up.
> Pubs is a sample database used in the documentation examples, and can be
> easily rebuilt. It should never need to be backed up at all. MSDB should
> be backed up so you can restore information about your tasks, jobs, alerts
> and backup history. But you may be backing up the full database already
> and it may only be the log backup that is failing.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
>
>|||Thanks for your prompt response, Jens. I just unchecked the backup for the
PUBS database. Thanks.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1140713647.322715.266680@.g47g2000cwa.googlegroups.com...
> MSDB stores all you job as well as replication information, so backin
> this up can save you lot of time in a disastery case. Pubs is jut a
> sample database, if you want to you can leave this out, as you can
> download the creation script somewhere on the MSDN space of microsoft.
> HTH, Jens Suessmeyer.
>
MSDB and PUBS Databases
We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Server.
We setup a SQL backup to run under SQL. We got the messages in the report.
It said "backup cannot be performed on database 'msdb'. This subtask is
ignored." and "Backup cannot be performed on database 'pubs'. This subtask
is ignored". Is it necessary to backup msdb and pubs databases? Thanks.
Hi Diane
My guess is that this error is occurring when you try to back up the
transaction log of these databases, as they are in simple mode and the log
cannot be backed up.
Pubs is a sample database used in the documentation examples, and can be
easily rebuilt. It should never need to be backed up at all. MSDB should be
backed up so you can restore information about your tasks, jobs, alerts and
backup history. But you may be backing up the full database already and it
may only be the log backup that is failing.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Server. We setup a SQL backup to run under SQL. We got the messages in
> the report. It said "backup cannot be performed on database 'msdb'. This
> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
> This subtask is ignored". Is it necessary to backup msdb and pubs
> databases? Thanks.
>
|||MSDB stores all you job as well as replication information, so backin
this up can save you lot of time in a disastery case. Pubs is jut a
sample database, if you want to you can leave this out, as you can
download the creation script somewhere on the MSDN space of microsoft.
HTH, Jens Suessmeyer.
|||Thank you very much, Kalen for your prompt response.
Under Database Maintenance, a complete backup runs once a week and
transaction backup runs everyday. You are right. The error message comes
from the transaction log history. Do you suggest that I ignore the error
messages since I have a complete backup runs every week? I will uncheck the
backup for the PUBS database.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eyN$1mJOGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Diane
> My guess is that this error is occurring when you try to back up the
> transaction log of these databases, as they are in simple mode and the log
> cannot be backed up.
> Pubs is a sample database used in the documentation examples, and can be
> easily rebuilt. It should never need to be backed up at all. MSDB should
> be backed up so you can restore information about your tasks, jobs, alerts
> and backup history. But you may be backing up the full database already
> and it may only be the log backup that is failing.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
>
>
|||Thanks for your prompt response, Jens. I just unchecked the backup for the
PUBS database. Thanks.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1140713647.322715.266680@.g47g2000cwa.googlegr oups.com...
> MSDB stores all you job as well as replication information, so backin
> this up can save you lot of time in a disastery case. Pubs is jut a
> sample database, if you want to you can leave this out, as you can
> download the creation script somewhere on the MSDN space of microsoft.
> HTH, Jens Suessmeyer.
>
We setup a SQL backup to run under SQL. We got the messages in the report.
It said "backup cannot be performed on database 'msdb'. This subtask is
ignored." and "Backup cannot be performed on database 'pubs'. This subtask
is ignored". Is it necessary to backup msdb and pubs databases? Thanks.
Hi Diane
My guess is that this error is occurring when you try to back up the
transaction log of these databases, as they are in simple mode and the log
cannot be backed up.
Pubs is a sample database used in the documentation examples, and can be
easily rebuilt. It should never need to be backed up at all. MSDB should be
backed up so you can restore information about your tasks, jobs, alerts and
backup history. But you may be backing up the full database already and it
may only be the log backup that is failing.
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Server. We setup a SQL backup to run under SQL. We got the messages in
> the report. It said "backup cannot be performed on database 'msdb'. This
> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
> This subtask is ignored". Is it necessary to backup msdb and pubs
> databases? Thanks.
>
|||MSDB stores all you job as well as replication information, so backin
this up can save you lot of time in a disastery case. Pubs is jut a
sample database, if you want to you can leave this out, as you can
download the creation script somewhere on the MSDN space of microsoft.
HTH, Jens Suessmeyer.
|||Thank you very much, Kalen for your prompt response.
Under Database Maintenance, a complete backup runs once a week and
transaction backup runs everyday. You are right. The error message comes
from the transaction log history. Do you suggest that I ignore the error
messages since I have a complete backup runs every week? I will uncheck the
backup for the PUBS database.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eyN$1mJOGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Diane
> My guess is that this error is occurring when you try to back up the
> transaction log of these databases, as they are in simple mode and the log
> cannot be backed up.
> Pubs is a sample database used in the documentation examples, and can be
> easily rebuilt. It should never need to be backed up at all. MSDB should
> be backed up so you can restore information about your tasks, jobs, alerts
> and backup history. But you may be backing up the full database already
> and it may only be the log backup that is failing.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
>
>
|||Thanks for your prompt response, Jens. I just unchecked the backup for the
PUBS database. Thanks.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1140713647.322715.266680@.g47g2000cwa.googlegr oups.com...
> MSDB stores all you job as well as replication information, so backin
> this up can save you lot of time in a disastery case. Pubs is jut a
> sample database, if you want to you can leave this out, as you can
> download the creation script somewhere on the MSDN space of microsoft.
> HTH, Jens Suessmeyer.
>
MSDB and PUBS Databases
We are running SQL 2000 Enterprise Edition on Windows 2003 Standard Server.
We setup a SQL backup to run under SQL. We got the messages in the report.
It said "backup cannot be performed on database 'msdb'. This subtask is
ignored." and "Backup cannot be performed on database 'pubs'. This subtask
is ignored". Is it necessary to backup msdb and pubs databases? Thanks.MSDB stores all you job as well as replication information, so backin
this up can save you lot of time in a disastery case. Pubs is jut a
sample database, if you want to you can leave this out, as you can
download the creation script somewhere on the MSDN space of microsoft.
HTH, Jens Suessmeyer.|||Hi Diane
My guess is that this error is occurring when you try to back up the
transaction log of these databases, as they are in simple mode and the log
cannot be backed up.
Pubs is a sample database used in the documentation examples, and can be
easily rebuilt. It should never need to be backed up at all. MSDB should be
backed up so you can restore information about your tasks, jobs, alerts and
backup history. But you may be backing up the full database already and it
may only be the log backup that is failing.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Server. We setup a SQL backup to run under SQL. We got the messages in
> the report. It said "backup cannot be performed on database 'msdb'. This
> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
> This subtask is ignored". Is it necessary to backup msdb and pubs
> databases? Thanks.
>|||Thank you very much, Kalen for your prompt response.
Under Database Maintenance, a complete backup runs once a week and
transaction backup runs everyday. You are right. The error message comes
from the transaction log history. Do you suggest that I ignore the error
messages since I have a complete backup runs every week? I will uncheck the
backup for the PUBS database.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eyN$1mJOGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Diane
> My guess is that this error is occurring when you try to back up the
> transaction log of these databases, as they are in simple mode and the log
> cannot be backed up.
> Pubs is a sample database used in the documentation examples, and can be
> easily rebuilt. It should never need to be backed up at all. MSDB should
> be backed up so you can restore information about your tasks, jobs, alerts
> and backup history. But you may be backing up the full database already
> and it may only be the log backup that is failing.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Server. We setup a SQL backup to run under SQL. We got the messages in
>> the report. It said "backup cannot be performed on database 'msdb'. This
>> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
>> This subtask is ignored". Is it necessary to backup msdb and pubs
>> databases? Thanks.
>>
>
>|||Thanks for your prompt response, Jens. I just unchecked the backup for the
PUBS database. Thanks.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1140713647.322715.266680@.g47g2000cwa.googlegroups.com...
> MSDB stores all you job as well as replication information, so backin
> this up can save you lot of time in a disastery case. Pubs is jut a
> sample database, if you want to you can leave this out, as you can
> download the creation script somewhere on the MSDN space of microsoft.
> HTH, Jens Suessmeyer.
>
We setup a SQL backup to run under SQL. We got the messages in the report.
It said "backup cannot be performed on database 'msdb'. This subtask is
ignored." and "Backup cannot be performed on database 'pubs'. This subtask
is ignored". Is it necessary to backup msdb and pubs databases? Thanks.MSDB stores all you job as well as replication information, so backin
this up can save you lot of time in a disastery case. Pubs is jut a
sample database, if you want to you can leave this out, as you can
download the creation script somewhere on the MSDN space of microsoft.
HTH, Jens Suessmeyer.|||Hi Diane
My guess is that this error is occurring when you try to back up the
transaction log of these databases, as they are in simple mode and the log
cannot be backed up.
Pubs is a sample database used in the documentation examples, and can be
easily rebuilt. It should never need to be backed up at all. MSDB should be
backed up so you can restore information about your tasks, jobs, alerts and
backup history. But you may be backing up the full database already and it
may only be the log backup that is failing.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Diane Walker" <ett9300@.yahoo.com> wrote in message
news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
> Server. We setup a SQL backup to run under SQL. We got the messages in
> the report. It said "backup cannot be performed on database 'msdb'. This
> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
> This subtask is ignored". Is it necessary to backup msdb and pubs
> databases? Thanks.
>|||Thank you very much, Kalen for your prompt response.
Under Database Maintenance, a complete backup runs once a week and
transaction backup runs everyday. You are right. The error message comes
from the transaction log history. Do you suggest that I ignore the error
messages since I have a complete backup runs every week? I will uncheck the
backup for the PUBS database.
Thanks.
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eyN$1mJOGHA.1124@.TK2MSFTNGP10.phx.gbl...
> Hi Diane
> My guess is that this error is occurring when you try to back up the
> transaction log of these databases, as they are in simple mode and the log
> cannot be backed up.
> Pubs is a sample database used in the documentation examples, and can be
> easily rebuilt. It should never need to be backed up at all. MSDB should
> be backed up so you can restore information about your tasks, jobs, alerts
> and backup history. But you may be backing up the full database already
> and it may only be the log backup that is failing.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Diane Walker" <ett9300@.yahoo.com> wrote in message
> news:utYsaWJOGHA.2472@.TK2MSFTNGP11.phx.gbl...
>> We are running SQL 2000 Enterprise Edition on Windows 2003 Standard
>> Server. We setup a SQL backup to run under SQL. We got the messages in
>> the report. It said "backup cannot be performed on database 'msdb'. This
>> subtask is ignored." and "Backup cannot be performed on database 'pubs'.
>> This subtask is ignored". Is it necessary to backup msdb and pubs
>> databases? Thanks.
>>
>
>|||Thanks for your prompt response, Jens. I just unchecked the backup for the
PUBS database. Thanks.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1140713647.322715.266680@.g47g2000cwa.googlegroups.com...
> MSDB stores all you job as well as replication information, so backin
> this up can save you lot of time in a disastery case. Pubs is jut a
> sample database, if you want to you can leave this out, as you can
> download the creation script somewhere on the MSDN space of microsoft.
> HTH, Jens Suessmeyer.
>
Subscribe to:
Posts (Atom)