Re: sql server 2005 std, maint plan for other database engines?

#41

If your Login is a member of "sysadmin" server fixed role, then you can
backup any database. If you Login is not a member of "sysadmin" then ensure
that your Login's mapped user is a member of db_backupoperator role in the
related database. And ensure that your SQL Server service has enough
permissions to write on the target folder on Server B. Also, ensure that you
are using UNC (which is like \\ServerB\SQLBackups)

If these suggesttions don't work for you, then let us know exactly what
error message you get when you try to backup your database to your ServerB

--
Ekrem Önsoy

"mat" <mat (AT) notarealdotcom (DOT) adr> wrote

Quote:

In article <4CD7F25F-F7F0-4BCF-AA42-54F383CB1651 (AT) microsoft (DOT) com>,
ekrem (AT) compecta (DOT) com says...
Hi mat,

You can create maintenance plans for your local server or remoteserver.
But
as it's mentioned in the post, there is no a connection dialog on the
Maintenance Plan Wizard to connect to remote databases.

Nevertheless, you can create this desired plan without the wizard. When
you
click on the Maintenance Plans on the Object Explorer a popup menu
appears.
Click "Create Maintenance Plan..." instead of the wizard. There, you'll
be
able to create different connections so that remote server databases will
be
reachable. Also, this is a more flexible way of creating richer and more
functional plans.

Thanks, skipping the wizard worked.

One oddity, backing up a sql express db on server A, from sql std server
on server B, I don't seem to be able to save the bak file to a dir on
server B. I can't see why not...why can't I save the file to a different
box than the one that's hosting the backed up db? Part of the idea is to
get the backup onto a different box in case of disk failure etc.

#42

If your Login is a member of "sysadmin" server fixed role, then you can
backup any database. If you Login is not a member of "sysadmin" then ensure
that your Login's mapped user is a member of db_backupoperator role in the
related database. And ensure that your SQL Server service has enough
permissions to write on the target folder on Server B. Also, ensure that you
are using UNC (which is like \\ServerB\SQLBackups)

If these suggesttions don't work for you, then let us know exactly what
error message you get when you try to backup your database to your ServerB

--
Ekrem Önsoy

"mat" <mat (AT) notarealdotcom (DOT) adr> wrote

Quote:

In article <4CD7F25F-F7F0-4BCF-AA42-54F383CB1651 (AT) microsoft (DOT) com>,
ekrem (AT) compecta (DOT) com says...
Hi mat,

You can create maintenance plans for your local server or remoteserver.
But
as it's mentioned in the post, there is no a connection dialog on the
Maintenance Plan Wizard to connect to remote databases.

Nevertheless, you can create this desired plan without the wizard. When
you
click on the Maintenance Plans on the Object Explorer a popup menu
appears.
Click "Create Maintenance Plan..." instead of the wizard. There, you'll
be
able to create different connections so that remote server databases will
be
reachable. Also, this is a more flexible way of creating richer and more
functional plans.

Thanks, skipping the wizard worked.

One oddity, backing up a sql express db on server A, from sql std server
on server B, I don't seem to be able to save the bak file to a dir on
server B. I can't see why not...why can't I save the file to a different
box than the one that's hosting the backed up db? Part of the idea is to
get the backup onto a different box in case of disk failure etc.

#43

If your Login is a member of "sysadmin" server fixed role, then you can
backup any database. If you Login is not a member of "sysadmin" then ensure
that your Login's mapped user is a member of db_backupoperator role in the
related database. And ensure that your SQL Server service has enough
permissions to write on the target folder on Server B. Also, ensure that you
are using UNC (which is like \\ServerB\SQLBackups)

If these suggesttions don't work for you, then let us know exactly what
error message you get when you try to backup your database to your ServerB

--
Ekrem Önsoy

"mat" <mat (AT) notarealdotcom (DOT) adr> wrote

Quote:

In article <4CD7F25F-F7F0-4BCF-AA42-54F383CB1651 (AT) microsoft (DOT) com>,
ekrem (AT) compecta (DOT) com says...
Hi mat,

You can create maintenance plans for your local server or remoteserver.
But
as it's mentioned in the post, there is no a connection dialog on the
Maintenance Plan Wizard to connect to remote databases.

Nevertheless, you can create this desired plan without the wizard. When
you
click on the Maintenance Plans on the Object Explorer a popup menu
appears.
Click "Create Maintenance Plan..." instead of the wizard. There, you'll
be
able to create different connections so that remote server databases will
be
reachable. Also, this is a more flexible way of creating richer and more
functional plans.

Thanks, skipping the wizard worked.

One oddity, backing up a sql express db on server A, from sql std server
on server B, I don't seem to be able to save the bak file to a dir on
server B. I can't see why not...why can't I save the file to a different
box than the one that's hosting the backed up db? Part of the idea is to
get the backup onto a different box in case of disk failure etc.

#44

If your Login is a member of "sysadmin" server fixed role, then you can
backup any database. If you Login is not a member of "sysadmin" then ensure
that your Login's mapped user is a member of db_backupoperator role in the
related database. And ensure that your SQL Server service has enough
permissions to write on the target folder on Server B. Also, ensure that you
are using UNC (which is like \\ServerB\SQLBackups)

If these suggesttions don't work for you, then let us know exactly what
error message you get when you try to backup your database to your ServerB

--
Ekrem Önsoy

"mat" <mat (AT) notarealdotcom (DOT) adr> wrote

Quote:

In article <4CD7F25F-F7F0-4BCF-AA42-54F383CB1651 (AT) microsoft (DOT) com>,
ekrem (AT) compecta (DOT) com says...
Hi mat,

You can create maintenance plans for your local server or remoteserver.
But
as it's mentioned in the post, there is no a connection dialog on the
Maintenance Plan Wizard to connect to remote databases.

Nevertheless, you can create this desired plan without the wizard. When
you
click on the Maintenance Plans on the Object Explorer a popup menu
appears.
Click "Create Maintenance Plan..." instead of the wizard. There, you'll
be
able to create different connections so that remote server databases will
be
reachable. Also, this is a more flexible way of creating richer and more
functional plans.

Thanks, skipping the wizard worked.

One oddity, backing up a sql express db on server A, from sql std server
on server B, I don't seem to be able to save the bak file to a dir on
server B. I can't see why not...why can't I save the file to a different
box than the one that's hosting the backed up db? Part of the idea is to
get the backup onto a different box in case of disk failure etc.

#45

If your Login is a member of "sysadmin" server fixed role, then you can
backup any database. If you Login is not a member of "sysadmin" then ensure
that your Login's mapped user is a member of db_backupoperator role in the
related database. And ensure that your SQL Server service has enough
permissions to write on the target folder on Server B. Also, ensure that you
are using UNC (which is like \\ServerB\SQLBackups)

If these suggesttions don't work for you, then let us know exactly what
error message you get when you try to backup your database to your ServerB

--
Ekrem Önsoy

"mat" <mat (AT) notarealdotcom (DOT) adr> wrote

Quote:

In article <4CD7F25F-F7F0-4BCF-AA42-54F383CB1651 (AT) microsoft (DOT) com>,
ekrem (AT) compecta (DOT) com says...
Hi mat,

You can create maintenance plans for your local server or remoteserver.
But
as it's mentioned in the post, there is no a connection dialog on the
Maintenance Plan Wizard to connect to remote databases.

Nevertheless, you can create this desired plan without the wizard. When
you
click on the Maintenance Plans on the Object Explorer a popup menu
appears.
Click "Create Maintenance Plan..." instead of the wizard. There, you'll
be
able to create different connections so that remote server databases will
be
reachable. Also, this is a more flexible way of creating richer and more
functional plans.

Thanks, skipping the wizard worked.

One oddity, backing up a sql express db on server A, from sql std server
on server B, I don't seem to be able to save the bak file to a dir on
server B. I can't see why not...why can't I save the file to a different
box than the one that's hosting the backed up db? Part of the idea is to
get the backup onto a different box in case of disk failure etc.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: sql server 2005 std, maint plan for other database engines?

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools

Re: sql server 2005 std, maint plan for other database engines? - 10-15-2008 , 09:16 AM

Re: sql server 2005 std, maint plan for other database engines? - 10-15-2008 , 09:16 AM

Re: sql server 2005 std, maint plan for other database engines? - 10-15-2008 , 09:16 AM

Re: sql server 2005 std, maint plan for other database engines? - 10-15-2008 , 09:16 AM

Re: sql server 2005 std, maint plan for other database engines? - 10-15-2008 , 09:16 AM