We have a SQL2000 database that is created via a dump from a third party
product. Being as this dump runs every day, we don't need to back up the
data. However we need the schema, views, triggers, etc. Everything except
the actual data in the tables. Is there a way to make a backup of this?
Thanks!
BrianYes, use some tool that generates DDL script for the database:
http://www.karaszi.com/SQLServer/info_generate_script.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Brian" <me@.here.there> wrote in message news:O%2323gnK8HHA.484@.TK2MSFTNGP06.phx.gbl...
> We have a SQL2000 database that is created via a dump from a third party product. Being as this
> dump runs every day, we don't need to back up the data. However we need the schema, views,
> triggers, etc. Everything except the actual data in the tables. Is there a way to make a backup of
> this?
> Thanks!
> Brian
>
Showing posts with label dump. Show all posts
Showing posts with label dump. Show all posts
Sunday, March 25, 2012
Backup Errors in sqlserver
Hello all,
How can I resolve this error message I keep getting when I try to backup my database?
Thanks in Advance.
"Can't open dump device 'D:\MSSQL\BACKUP\dmpApp_tracker.DAT', device error or device off line. Please consult the SQL Server error log for more details. (Message 3201)"Are you appending to the device? I've seen this happen when an active backup operation gets interrupted. After that the device needs to be re-created. If you were appending backups to it see if you can recover the ones that you intend to keep.|||No, I am not appending to it. This is sqlserver 6.5 and it does not give you that option. It does have a expire after date and I set that to 7. Thanks for the help.|||6.5?
Deal me out...
What did the error log say?|||Yes it does! WITH NOINIT is available in 6.5 SP5a, look closely!
How can I resolve this error message I keep getting when I try to backup my database?
Thanks in Advance.
"Can't open dump device 'D:\MSSQL\BACKUP\dmpApp_tracker.DAT', device error or device off line. Please consult the SQL Server error log for more details. (Message 3201)"Are you appending to the device? I've seen this happen when an active backup operation gets interrupted. After that the device needs to be re-created. If you were appending backups to it see if you can recover the ones that you intend to keep.|||No, I am not appending to it. This is sqlserver 6.5 and it does not give you that option. It does have a expire after date and I set that to 7. Thanks for the help.|||6.5?
Deal me out...
What did the error log say?|||Yes it does! WITH NOINIT is available in 6.5 SP5a, look closely!
Sunday, February 12, 2012
Backing up Transaction log
Is there a way to backup a Transaction log without actually saving with the
backup utility. All I really want to do is dump the log. Thanks.Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
--
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
backup utility. All I really want to do is dump the log. Thanks.Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
--
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
Backing up Transaction log
Is there a way to backup a Transaction log without actually saving with the
backup utility. All I really want to do is dump the log. Thanks.
Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
backup utility. All I really want to do is dump the log. Thanks.
Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
Backing up Transaction log
Is there a way to backup a Transaction log without actually saving with the
backup utility. All I really want to do is dump the log. Thanks.Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
backup utility. All I really want to do is dump the log. Thanks.Tom,
Try NO_LOG or TRUNCATE_ONLY. For more information see the Truncating the
Transaction Log topic in the SQL Server BOL.
HTH
Jerry
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>|||Tom Reis wrote:
> Is there a way to backup a Transaction log without actually saving
> with the backup utility. All I really want to do is dump the log.
> Thanks.
Use the with truncate_only option. The log is truncated and no backup
actually occurs. You'll need to perform a full database backup to get
back on track.
David Gugick
Quest Software
www.imceda.com
www.quest.com|||If that is the case why are you in FULL recovery mode to begin with? As
soon as you manually truncate the log you loose the ability to use the log
for recovery purposes. So if you are not planning on issuing regular log
backups you should set the recovery mode to Simple and it will automatically
truncate the log when it gets to 70% full.
Andrew J. Kelly SQL MVP
"Tom Reis" <reistom@.cdnet.cod.edu> wrote in message
news:ud6$kBtuFHA.3124@.TK2MSFTNGP10.phx.gbl...
> Is there a way to backup a Transaction log without actually saving with
> the
> backup utility. All I really want to do is dump the log. Thanks.
>
Friday, February 10, 2012
backing up to network share issue.
Hi,
As mentioned in a previous post, I am trying to backup to a network drive. When I add the dump device using the unc and try to backup, I get the following error message "cannot open backup device. Device error or device off-line.." So I did research on
this error and found out a MS kb which states that this might be happening if I do not have write access to that drive. Now I do have write access there but I know it has something to do with SQL Server trying to write to that shared drive in disguise of
local account instead of me.. (as account). Now, another article here http://www.winnetmag.com/Article/Art...025/14025.html describes what needs to be done but the problem is that I can do all this at my office. But we are creating shrink wrapped
app using MSDE and we will be providing a simple user interface to the client to do backup/restore. So what should I tell my clients or even best what should I do so that the backups to the network share work seemlessly.
The quest is unsatiable!!
This is really a windows issue, not a SQL Server issue. Every piece of software runs under a user account in
Windows (NT). And every user who accesses a resource (like a share) need permissions to that resource. If the
software (user) - SQL Server in this case - doesn't have access to the share, then Windows will not allow
access. You have to make sure that SQL Server is using an account that has permissions on the share in
question.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"whynot" <anonymous@.discussions.microsoft.com> wrote in message
news:92D21681-63A8-40DD-8C86-583DA99F27FB@.microsoft.com...
> Hi,
> As mentioned in a previous post, I am trying to backup to a network drive. When I add the dump device using
the unc and try to backup, I get the following error message "cannot open backup device. Device error or
device off-line.." So I did research on this error and found out a MS kb which states that this might be
happening if I do not have write access to that drive. Now I do have write access there but I know it has
something to do with SQL Server trying to write to that shared drive in disguise of local account instead of
me.. (as account). Now, another article here http://www.winnetmag.com/Article/Art...025/14025.html
describes what needs to be done but the problem is that I can do all this at my office. But we are creating
shrink wrapped app using MSDE and we will be providing a simple user interface to the client to do
backup/restore. So what should I tell my clients or even best what should I do so that the backups to the
network share work seemlessly.
> The quest is unsatiable!!
As mentioned in a previous post, I am trying to backup to a network drive. When I add the dump device using the unc and try to backup, I get the following error message "cannot open backup device. Device error or device off-line.." So I did research on
this error and found out a MS kb which states that this might be happening if I do not have write access to that drive. Now I do have write access there but I know it has something to do with SQL Server trying to write to that shared drive in disguise of
local account instead of me.. (as account). Now, another article here http://www.winnetmag.com/Article/Art...025/14025.html describes what needs to be done but the problem is that I can do all this at my office. But we are creating shrink wrapped
app using MSDE and we will be providing a simple user interface to the client to do backup/restore. So what should I tell my clients or even best what should I do so that the backups to the network share work seemlessly.
The quest is unsatiable!!
This is really a windows issue, not a SQL Server issue. Every piece of software runs under a user account in
Windows (NT). And every user who accesses a resource (like a share) need permissions to that resource. If the
software (user) - SQL Server in this case - doesn't have access to the share, then Windows will not allow
access. You have to make sure that SQL Server is using an account that has permissions on the share in
question.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"whynot" <anonymous@.discussions.microsoft.com> wrote in message
news:92D21681-63A8-40DD-8C86-583DA99F27FB@.microsoft.com...
> Hi,
> As mentioned in a previous post, I am trying to backup to a network drive. When I add the dump device using
the unc and try to backup, I get the following error message "cannot open backup device. Device error or
device off-line.." So I did research on this error and found out a MS kb which states that this might be
happening if I do not have write access to that drive. Now I do have write access there but I know it has
something to do with SQL Server trying to write to that shared drive in disguise of local account instead of
me.. (as account). Now, another article here http://www.winnetmag.com/Article/Art...025/14025.html
describes what needs to be done but the problem is that I can do all this at my office. But we are creating
shrink wrapped app using MSDE and we will be providing a simple user interface to the client to do
backup/restore. So what should I tell my clients or even best what should I do so that the backups to the
network share work seemlessly.
> The quest is unsatiable!!
Subscribe to:
Posts (Atom)