Msde and backup-restore

I'm using Msde on a PC with XP SP2 acting as "server" and accessing a
database on a PC with XP SP2 acting as "client". I can backup my database
from the "client" using UNC format
"\\client.computer.name\share.name\file.name.b kp" but when trying to restore
it from the "client" PC i get errors. Any ideas about how to restore the bkp
file to server pc from the client without having to copy the bkp file to the
server and perform the restore from there? Thanks
hi,
Dithom wrote:
> I'm using Msde on a PC with XP SP2 acting as "server" and accessing a
> database on a PC with XP SP2 acting as "client". I can backup my
> database from the "client" using UNC format
> "\\client.computer.name\share.name\file.name.b kp" but when trying to
> restore it from the "client" PC i get errors. Any ideas about how to
> restore the bkp file to server pc from the client without having to
> copy the bkp file to the server and perform the restore from there?
> Thanks
what kind of exception do you get?
actually if you can backup on a remote share you should be able to restore
from it too..
the account(s) running the SQL Server and SQL Server Agent must have enought
privileges on the remote share...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE 2000 and SQL2005

I have to install MSDE 2000 with a backup application (CommVault Express
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:

> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website
I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the serve
r
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:

> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Serve
r
> performance, your computer may need much more memory and disk space for th
e
> coexistance.
> Please feel free to let us know if you need further assistance. Have a goo
d
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>

MSDE 2000 and SQL2005

I have to install MSDE 2000 with a backup application (CommVault Express
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.
I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:

> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>
|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the server
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:

> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Server
> performance, your computer may need much more memory and disk space for the
> coexistance.
> Please feel free to let us know if you need further assistance. Have a good
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
sql

MSDE 2000 and SQL2005

I have to install MSDE 2000 with a backup application (CommVault Express
6.1) that does not yet support SQL 2005. I also need to install 2005 for
apps that will utilize this version. Are there any known problems with
running both of these versions of SQL on the same server?
Thanks,
Mark B.I have installed 2000 & 2005 on the same server before and they both work.
The 2000 install is the default instance and the 2005 is the named instance.
The only issue might be whether your server has enough resources to handle
both. Memory in particular. I don't think that both instaces share the same
memory space so you would have to make sure there is enough for both.
"Mark Bohlsen" wrote:
> I have to install MSDE 2000 with a backup application (CommVault Express
> 6.1) that does not yet support SQL 2005. I also need to install 2005 for
> apps that will utilize this version. Are there any known problems with
> running both of these versions of SQL on the same server?
> Thanks,
> Mark B.
>
>|||Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
with SQL Server 2005 instances on the same computer. Considering SQL Server
performance, your computer may need much more memory and disk space for the
coexistance.
Please feel free to let us know if you need further assistance. Have a good
day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||What about MSDE 2000 and SQL 2000 on the same server? Almost every website I
read on this topic says something different.
I have a server that currently runs two named instances of MSDE 2000 SP3a.
I want to install SQL2000 (as the default instance) on the server (the server
is light duty, but has 3GB of RAM). I'd imagine I could upgrade the MSDE
databases to SQL 2000 first, but I rather not since the MSDE instances are
working fine.
- Kevin
"Charles Wang[MSFT]" wrote:
> Yes, I agree with Michael. SQL Server 2000 including MSDE2000 can coexist
> with SQL Server 2005 instances on the same computer. Considering SQL Server
> performance, your computer may need much more memory and disk space for the
> coexistance.
> Please feel free to let us know if you need further assistance. Have a good
> day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>

MSDE + SSL

Hi!
I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003 OWA.
I installed SP1 for Win2003, WSUS and I created a certificate for OWA with
help from SelfSSL.
After this, I cant start my Backup Exec services, complaining about some SSL
error:
SSL Security error
ConnectionOpen (SECDoHandshake()).
and
[DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
I think all this is a problem with SSL and MSDE.
Veritas says "talk to Microsoft" and gues what MS says...
What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE (8.0)
run nice beside SSL for our OWA access.
Thanks!
Mattias
hi Mattias,
MrM wrote:
> Hi!
> I had a working Win2003 server with Backup Exec 9.1 and Exchange 2003
> OWA. I installed SP1 for Win2003, WSUS and I created a certificate
> for OWA with help from SelfSSL.
> After this, I cant start my Backup Exec services, complaining about
> some SSL error:
> --
> SSL Security error
> ConnectionOpen (SECDoHandshake()).
> and
> [DBNETLIB][ConnectionOpen (SECDoHandshake()).]SSL Security error.
> --
> I think all this is a problem with SSL and MSDE.
> Veritas says "talk to Microsoft" and gues what MS says...
> What does SelfSSL to do with MSDE? Or what shoult I do to make MSDE
> (8.0) run nice beside SSL for our OWA access.
>
please try having a look at
http://support.microsoft.com/default.aspx?id=309398 and
http://www.fftf.org/news/Aug05feed/M...ouble.rss.html
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE (SQL) Backup

Not sure if this really if the right forum but i have a question about MSDE.
When backing it up do you generally need a database agent for the backup
software?
more specifically, if you are backing up a server, with MSDE databases,
using Tivoli Storage Managers do you need the Databases module? (the databas
e
module specifically mentions only SQL)Hi
If you want to schedule your backup database , so yes you need SQL Server
Agent
"Michlong" <Michlong@.discussions.microsoft.com> wrote in message
news:6E737ABC-6596-4996-8312-46FBAF516E75@.microsoft.com...
> Not sure if this really if the right forum but i have a question about
> MSDE.
> When backing it up do you generally need a database agent for the backup
> software?
> more specifically, if you are backing up a server, with MSDE databases,
> using Tivoli Storage Managers do you need the Databases module? (the
> database
> module specifically mentions only SQL)|||You don't absolutely need a database backup agent for MSDE. You can use
the native BACKUP command or, if you can afford to take the database
offline during backup, you can just backup the database files from the
filesystem.
The advantage of using the Tivoli Data Protection module is that it
allows integration with the Tivoli storage management software.
I really don't know whether Tivoli supports MSDE, I've only used it
with SQL Server Enterprise, you'll have to check with IBM or your
vendor.
David Portas
SQL Server MVP
--

MSDE (SQL) Backup

Not sure if this really if the right forum but i have a question about MSDE.
When backing it up do you generally need a database agent for the backup
software?
more specifically, if you are backing up a server, with MSDE databases,
using Tivoli Storage Managers do you need the Databases module? (the database
module specifically mentions only SQL)
Hi
If you want to schedule your backup database , so yes you need SQL Server
Agent
"Michlong" <Michlong@.discussions.microsoft.com> wrote in message
news:6E737ABC-6596-4996-8312-46FBAF516E75@.microsoft.com...
> Not sure if this really if the right forum but i have a question about
> MSDE.
> When backing it up do you generally need a database agent for the backup
> software?
> more specifically, if you are backing up a server, with MSDE databases,
> using Tivoli Storage Managers do you need the Databases module? (the
> database
> module specifically mentions only SQL)
|||You don't absolutely need a database backup agent for MSDE. You can use
the native BACKUP command or, if you can afford to take the database
offline during backup, you can just backup the database files from the
filesystem.
The advantage of using the Tivoli Data Protection module is that it
allows integration with the Tivoli storage management software.
I really don't know whether Tivoli supports MSDE, I've only used it
with SQL Server Enterprise, you'll have to check with IBM or your
vendor.
David Portas
SQL Server MVP

MSDE (SQL) Backup

Not sure if this really if the right forum but i have a question about MSDE.
When backing it up do you generally need a database agent for the backup
software?
more specifically, if you are backing up a server, with MSDE databases,
using Tivoli Storage Managers do you need the Databases module? (the database
module specifically mentions only SQL)Hi
If you want to schedule your backup database , so yes you need SQL Server
Agent
"Michlong" <Michlong@.discussions.microsoft.com> wrote in message
news:6E737ABC-6596-4996-8312-46FBAF516E75@.microsoft.com...
> Not sure if this really if the right forum but i have a question about
> MSDE.
> When backing it up do you generally need a database agent for the backup
> software?
> more specifically, if you are backing up a server, with MSDE databases,
> using Tivoli Storage Managers do you need the Databases module? (the
> database
> module specifically mentions only SQL)|||You don't absolutely need a database backup agent for MSDE. You can use
the native BACKUP command or, if you can afford to take the database
offline during backup, you can just backup the database files from the
filesystem.
The advantage of using the Tivoli Data Protection module is that it
allows integration with the Tivoli storage management software.
I really don't know whether Tivoli supports MSDE, I've only used it
with SQL Server Enterprise, you'll have to check with IBM or your
vendor.
--
David Portas
SQL Server MVP
--

MSDE - moving a copy of a database and reloading onto another PC

I need to the best way to make a copy(Backup/export) of the data base put in on a CD or e-mail it. Have instructions to import or restore the database onto another PC.
Also in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn>
What and how does dtsrun.exe work?
Thanks
These articles might help ..
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||These articles might help ..
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

MSDE - moving a copy of a database and reloading onto another PC

I need to the best way to make a copy(Backup/export) of the data base put in on a CD or e-mail it. Have instructions to import or restore the database onto another PC.
Also in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn>
What and how does dtsrun.exe work?
Thanks
Please refer to these articles that might help -
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||Please refer to these articles that might help -
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
240872 HOW TO: Resolve Permission Issues When You Move a Database Between
http://support.microsoft.com/?id=240872
Cheers,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

MSDE

How about backup with MSDE?
is there some utility for it?
tnxYou can use the OSQL.EXE command with the appropiate BACKUP statement
to backup the database. The syntax of the command is explained in the
BOL of SQL Server.

HTH, Jens Suessmeyer.

--
http://www.sqlserver2005.de
--|||You can use the OSQL.EXE command with the appropiate BACKUP statement
to backup the database. The syntax of the command is explained in the
BOL of SQL Server.

HTH, Jens Suessmeyer.

--
http://www.sqlserver2005.de
--

msdb.dbo.sysdbmaintplan_history table question

Hi,
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are f
ound. Make sure you
handle the job so your are notified if errors occurs.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroup
s.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mar
k the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint
plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doi
ng the backup to the
"nul" file name?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor_y has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor_y table ?
Many Thanks
--Sam

msdb.dbo.sysdbmaintplan_history table question

Hi,
I am trying to check that a backup integrity check has verified a log
backup because it is being done over a network drive.
There is an entry verify backup for each backup performed in the
msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
correct one I should be looking at to see if RESTORE VERIFYONLY
succeeded ?
My question is how do I tell that a verification found an error?
Thanks
--SamMaint plan executed RESTORE VERIFYONLY. It will produce errors of such are found. Make sure you
handle the job so your are notified if errors occurs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message news:1147179633.997410.37830@.j73g2000cwa.googlegroups.com...
> Hi,
> I am trying to check that a backup integrity check has verified a log
> backup because it is being done over a network drive.
> There is an entry verify backup for each backup performed in the
> msdb.dbo.sysdbmaintplan_history table. Is the verify backup entry the
> correct one I should be looking at to see if RESTORE VERIFYONLY
> succeeded ?
> My question is how do I tell that a verification found an error?
> Thanks
> --Sam
>|||Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor=ADy has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor=ADy table ?
Many Thanks
--Sam|||I don't know, I'm afraid. I'd guess that Maint plans are smart enough to mark the execution as
failed and log the errors returned by RESTORE VERIFYONLY. I don't use maint plans myself, as I
prefer more control over these things. Perhaps you can try, for instance doing the backup to the
"nul" file name?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<wildturtle@.gmail.com> wrote in message
news:1147180762.992024.182010@.u72g2000cwu.googlegroups.com...
Thanks for your reply. My problem is the following:
the msdb.dbo.sysdbmaintplan_histor­y has two records: "Backup
transaction log" and "Verify Backup". They both have fields
called succeeded, error, and message. my question is, if a RESTORE
VERIFYONLY were to detect corruption, how would that be reflected
in the sysdbmaintplan_histor­y table ?
Many Thanks
--Sam

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:

> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msd
b
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will n
ot
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.
Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:

> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>
|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi
|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

msdb trascation logging mode

Hi,
I have a production SQL 2000 database with transaction logging turned on
('Full' recovery mode). I backup the transaction log every 15 minutes. In
order to use the point-in-time recovery option, do I also need to have the
'Full' recovery model set on the msdb? I ask this because I assume the msdb
holds information about the transaction log backup taken on the production
database. Without this information, I suspect point-in-time recover will not
be possible. Is my assumption correct?
Regards,
James G.Hi
MSDB is not needed to do point in time recovery. MSDB is just used to keep
the backup information so that Enterprise Manager UI can show you what
backups are available. It is a nice to have.
Point in time recovery needs the database dump and all the transaction log
dumps after that to the time you want to restore to.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"James Goodwill" wrote:
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>|||Hi James
The MSDB doesn't have to be in full recovery mode. In fact the MSDB
has no role when you run the restore. If the MSDB would have any role
in the restore then it would be impossible to restore the database on a
different server. All the data that is needed for the point in time
restore is stored in the log backup it self.
Adi|||Hi,
'Full' recovery model set on the msdb?
Ans:- NO NEED
I suspect point-in-time recover will not be possible. Is my assumption
correct?
No. You can do it with out a MSDB tranasction log backup.
--
MSDB database holds the backup history information. FOR each backup SQL
Server logs an entry into BACKUPSET table in MSDB database.
This is just an information only and will be useful if you use Enterprise
manager to do point in time recovery. Even if you
do not have tis information you can do a recovery based on Transaction log
file date and time. For a time based recovery:-
1. Restore the Full database backup first with Norecovery
2. Restore the logbackup file in sequence based on date and time with
Norecovery till last file
3. Restore the last transaction log backup with RECOVERY and STOPAT option.
Note:-
I am taking the MSDB full database backup daily once only.
Thanks
Hari
SQL Server MVP
"James Goodwill" <james.goodwill@.uk.fujitsu.com> wrote in message
news:DmmHe.10993$SO4.8738@.newsfe4-win.ntli.net...
> Hi,
> I have a production SQL 2000 database with transaction logging turned on
> ('Full' recovery mode). I backup the transaction log every 15 minutes. In
> order to use the point-in-time recovery option, do I also need to have the
> 'Full' recovery model set on the msdb? I ask this because I assume the
> msdb
> holds information about the transaction log backup taken on the production
> database. Without this information, I suspect point-in-time recover will
> not
> be possible. Is my assumption correct?
> Regards,
> James G.
>
>

MSDB suspect

Hi,
What are the steps I should execute if MSDB database is showing suspect.
The conditions is we dont have a backup but the sqlserver is running.Look at the sql server logs and see what might have caused this. Look in bol for sp_resetstatus. Worst case scenario, you will have to detach the msdb and run instmsdb.sql to recreate (however, you will lose all information stored in the msdb - DTS packages, scheduled tasks, backup/restore history, replication).

Oh yes - One last step - BACKUP ... :-)

msdb restore to standby server

Can the msdb database safely be moved to a new server by taking a backup fro
m
the source server and restoring to the target? I am aware that
sysjobs.originating_server must be updated after the restore and that
Microsoft suggests transfering the msdb by scripting jobs, dts packages, etc
.SQL Server 2000 sp3
"Brandon" wrote:

> Can the msdb database safely be moved to a new server by taking a backup f
rom
> the source server and restoring to the target? I am aware that
> sysjobs.originating_server must be updated after the restore and that
> Microsoft suggests transfering the msdb by scripting jobs, dts packages, e
tc.
>|||Ive never had good luck doing that and just would up going the MS route.
--
TIA,
ChrisR
"Brandon" wrote:

> Can the msdb database safely be moved to a new server by taking a backup f
rom
> the source server and restoring to the target? I am aware that
> sysjobs.originating_server must be updated after the restore and that
> Microsoft suggests transfering the msdb by scripting jobs, dts packages, e
tc.
>

msdb restore to standby server

Can the msdb database safely be moved to a new server by taking a backup from
the source server and restoring to the target? I am aware that
sysjobs.originating_server must be updated after the restore and that
Microsoft suggests transfering the msdb by scripting jobs, dts packages, etc.
SQL Server 2000 sp3
"Brandon" wrote:

> Can the msdb database safely be moved to a new server by taking a backup from
> the source server and restoring to the target? I am aware that
> sysjobs.originating_server must be updated after the restore and that
> Microsoft suggests transfering the msdb by scripting jobs, dts packages, etc.
>
|||Ive never had good luck doing that and just would up going the MS route.
TIA,
ChrisR
"Brandon" wrote:

> Can the msdb database safely be moved to a new server by taking a backup from
> the source server and restoring to the target? I am aware that
> sysjobs.originating_server must be updated after the restore and that
> Microsoft suggests transfering the msdb by scripting jobs, dts packages, etc.
>

msdb restore to standby server

Can the msdb database safely be moved to a new server by taking a backup from
the source server and restoring to the target? I am aware that
sysjobs.originating_server must be updated after the restore and that
Microsoft suggests transfering the msdb by scripting jobs, dts packages, etc.SQL Server 2000 sp3
"Brandon" wrote:
> Can the msdb database safely be moved to a new server by taking a backup from
> the source server and restoring to the target? I am aware that
> sysjobs.originating_server must be updated after the restore and that
> Microsoft suggests transfering the msdb by scripting jobs, dts packages, etc.
>|||Ive never had good luck doing that and just would up going the MS route.
--
TIA,
ChrisR
"Brandon" wrote:
> Can the msdb database safely be moved to a new server by taking a backup from
> the source server and restoring to the target? I am aware that
> sysjobs.originating_server must be updated after the restore and that
> Microsoft suggests transfering the msdb by scripting jobs, dts packages, etc.
>