I used backup and restore to upgrade a database from sql 2000 to sql 2005. Is it necessary to create the mdf and ldf on the new server at the time of restore under options or should I copy them to the new server in the data folder? I am new and not quite sure what the log files hold.
Thanksif you have created a backup of a database, you don't need anything but the .bak file.
when you restore from a bak file, the data and log files will be created automatically by the server.|||Edit: You don't need to create them, the restore does.
How backup works:
When SQL Server backs up a database, it backs up the data file first. During the backup of the data file, no changes are written to the data file, only to the log. When the bacup of the data file is complete, the changes written to the log file is backed up. In other words, backup of a SQL Server restores to the point of time when the backup finished, not started. Furthermore, your log file will be used to keep track of transactions afer the backup have restored, so you will need the file.|||Ok. If I don't specify in options at the time of restore, I can't find where the the mdf and ldf files were created. And are these new mdf and ldf files or do they hold the same data as the database before they were created on the new server.
thanks|||this will tell you where they are:
exec sp_helpfile
Showing posts with label necessary. Show all posts
Showing posts with label necessary. Show all posts
Thursday, March 8, 2012
Saturday, February 25, 2012
Backup and Restore
Running SQL Server 2K. I use transactional Replication.
It is sometimes necessary to take precautionary backups during
business hours for various reasons. However, I have noted
that backups made while replication is running can not be made
without causing an error during Restore. Is there a
workaround for this, or does Replication need to be diabled
prior to
backup?
Thanks,
Tom
Tom,
if you mean the error from the Log Reader Agent because it detects that the
Distributor is ahead of the Publisher, you can run sp_replrestart in the
publication database with no parameters. This forces replication to continue
even if the Distributor and some Subscribers may now have data that the
Publisher no longer has. If not, please can you post up the error message.
HTH,
Paul Ibison
|||exactly what is the error you get during the restore?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
<tkane@.yamner.com> wrote in message
news:c14f01c4385d$32a6e950$a401280a@.phx.gbl...
> Running SQL Server 2K. I use transactional Replication.
> It is sometimes necessary to take precautionary backups during
> business hours for various reasons. However, I have noted
> that backups made while replication is running can not be made
> without causing an error during Restore. Is there a
> workaround for this, or does Replication need to be diabled
> prior to
> backup?
> Thanks,
> Tom
It is sometimes necessary to take precautionary backups during
business hours for various reasons. However, I have noted
that backups made while replication is running can not be made
without causing an error during Restore. Is there a
workaround for this, or does Replication need to be diabled
prior to
backup?
Thanks,
Tom
Tom,
if you mean the error from the Log Reader Agent because it detects that the
Distributor is ahead of the Publisher, you can run sp_replrestart in the
publication database with no parameters. This forces replication to continue
even if the Distributor and some Subscribers may now have data that the
Publisher no longer has. If not, please can you post up the error message.
HTH,
Paul Ibison
|||exactly what is the error you get during the restore?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
<tkane@.yamner.com> wrote in message
news:c14f01c4385d$32a6e950$a401280a@.phx.gbl...
> Running SQL Server 2K. I use transactional Replication.
> It is sometimes necessary to take precautionary backups during
> business hours for various reasons. However, I have noted
> that backups made while replication is running can not be made
> without causing an error during Restore. Is there a
> workaround for this, or does Replication need to be diabled
> prior to
> backup?
> Thanks,
> Tom
Labels:
backup,
backups,
database,
duringbusiness,
microsoft,
mysql,
necessary,
oracle,
precautionary,
replication,
restore,
running,
server,
sql,
transactional,
various
Backup and Restiore
Running SQL Server 2K. I use transactional Replication.
It is sometimes necessary to take precautionary backups
during business hours for various reasons. However, I have
noted that backups made while replication is running can
not be made without causing an error during Restore. Is
there a workaround for this, or does Replication need to be
diabled prior to backup?
Thanks,
TomWhat error do you see during restore? To keep replication during a restore
you have to use TSQL and specify the KEEP_Replication option. However,
without this option it should restore fine, it will just strip out the
replication. The option is not available in Enterprise Manager.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
It is sometimes necessary to take precautionary backups
during business hours for various reasons. However, I have
noted that backups made while replication is running can
not be made without causing an error during Restore. Is
there a workaround for this, or does Replication need to be
diabled prior to backup?
Thanks,
TomWhat error do you see during restore? To keep replication during a restore
you have to use TSQL and specify the KEEP_Replication option. However,
without this option it should restore fine, it will just strip out the
replication. The option is not available in Enterprise Manager.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Labels:
backup,
backupsduring,
business,
database,
microsoft,
mysql,
necessary,
oracle,
precautionary,
replication,
restiore,
running,
server,
sql,
transactional,
various
Subscribe to:
Posts (Atom)