BACKUP DATABASE?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"John" <John@.nospam.infovis.co.uk> wrote in message news:eoAZqSDhHHA.4552@.TK2MSFTNGP04.phx.gbl...
> Hi
> Is there a way to dump all the sql server data into some sort of file that
> can be imported into a local sql server later? I have used sql server dumper
> but it is not very stable and crashes during sump.
> Thanks
> Regards
>
Hi John
"John" wrote:
> Remote, does not work for some reason possibly insufficient rights.
>
If you want to post the command you are using it may help? Also the full
error message would be useful. If you want the backup to be placed on a
different server you can use a UNC path. Make sure that you also have
directory permissions as well as server/database permissions sysadmin,
db_owner or db_backupoperator. See BACKUP in Books Online for more.
Databases can also be detached and attached, it is usually best to attach
the database to an instance at the same service pack/hotfix number, but SQL
2000 databases can be attached to SQL 2005 instances, although you may have
to change incompatibilities if you want to use the latest compatibility mode.
If you are changing instance you will need to script logins and possibly
resolved orphaned users see
http://support.microsoft.com/default.aspx/kb/314546 for more.
John
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:eQl9syDhHHA.392@.TK2MSFTNGP06.phx.gbl...
>
>
|||Can't you backup the database to a file local on the SQL Server machine and then FTP the file to
your machine?
Other methods include script out all the objects and data and then re-create the objects locally and
then import that data. I doubt you will find something as such as rock solid as backup. I've listed
some tools to generate scripts and some with data at
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
"John" <John@.nospam.infovis.co.uk> wrote in message
news:%234nMS%23DhHHA.4692@.TK2MSFTNGP04.phx.gbl...
> Remote, does not work for some reason possibly insufficient rights.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:eQl9syDhHHA.392@.TK2MSFTNGP06.phx.gbl...
>
Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts
Wednesday, March 21, 2012
Sunday, March 11, 2012
Duble \\ in physical file name
I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
Duble \\ in physical file name
I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. Laoyan
Generally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. Laoyan
Generally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
Duble \\ in physical file name
I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thin
g
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thin
g
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan
Sunday, February 26, 2012
DtsBackup2000 for SSIS packages?
hi everyone,
Up to moment I've been using Dtsbackup2000 for do backup for our DTS but now, which let's allow do the same with dtsx?
TIA
I don't realize and I've deleted a package. If I would have a backup I could restore it as in old times by dtb/dts|||If its a .dtsx file then a file system backup will do the job.
-Jamie
|||you're right
Subscribe to:
Posts (Atom)