Moving backup devices

Is there a way to copy backup devices between 2 servers with a script or
something else ? I actually need to move my current installation on a new
server and I don't want to recreate 200 backup devices manually.
Thanks in advance
script out the sysdevices table... eg
USE master
GO
SELECT *
FROM dbo.sysdevices

Moving backup devices

Is there a way to copy backup devices between 2 servers with a script or
something else ? I actually need to move my current installation on a new
server and I don't want to recreate 200 backup devices manually.
Thanks in advancescript out the sysdevices table... eg
USE master
GO
SELECT *
FROM dbo.sysdevices

Moving backup devices

Is there a way to copy backup devices between 2 servers with a script or
something else ? I actually need to move my current installation on a new
server and I don't want to recreate 200 backup devices manually.
Thanks in advancescript out the sysdevices table... eg
USE master
GO
SELECT *
FROM dbo.sysdevices

Moving 2005 Resource Database

We have a sql 2005 installation that has service pack 2 applied. All
the system databases apart from the resource database have been moved
from the default data directory to our own data directory on a
seperate drive and this went ok. We've done this basically to make the
back up process more efficient in our environment. The issue is that
we cant find a way to move the resource database to the new location
and this I beleive needs to be kept with the master database. We've
followed the BOL instructions for moving system databases but the
Alter script for the resource database fails as the resource database
doesnt exist in sysdatabases. I've tried simply moving the resource
files to the new location but then sql wont start as it cant find the
files.
Anybody have any ideas how to resolve this issue?
Thanks
MichaelThe instructions in Books Online for moving the master and resource database
files should work. However, we made some corrections to the procedure in
April 2006. If you don't have the latest version of Books Online, you might
be running into a problem.
I suggest that you download the latest version fo BOL (see the link in my
signature) and then starting with step 7 (Start the instance of SQL Server
in master-only recovery mode...), see if you can get the resource database
moved. If you still run into trouble, please report the exact error
message you're getting.
Regards,
Gail
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Download the latest version of Books Online from
http://www.microsoft.com/technet/pr...oads/books.mspx
"Michael" <michael@.hampel.fsnet.co.uk> wrote in message
news:1183985960.779841.257510@.k79g2000hse.googlegroups.com...
> We have a sql 2005 installation that has service pack 2 applied. All
> the system databases apart from the resource database have been moved
> from the default data directory to our own data directory on a
> seperate drive and this went ok. We've done this basically to make the
> back up process more efficient in our environment. The issue is that
> we cant find a way to move the resource database to the new location
> and this I beleive needs to be kept with the master database. We've
> followed the BOL instructions for moving system databases but the
> Alter script for the resource database fails as the resource database
> doesnt exist in sysdatabases. I've tried simply moving the resource
> files to the new location but then sql wont start as it cant find the
> files.
> Anybody have any ideas how to resolve this issue?
> Thanks
> Michael
>

Moving 2005 Resource Database

We have a sql 2005 installation that has service pack 2 applied. All
the system databases apart from the resource database have been moved
from the default data directory to our own data directory on a
seperate drive and this went ok. We've done this basically to make the
back up process more efficient in our environment. The issue is that
we cant find a way to move the resource database to the new location
and this I beleive needs to be kept with the master database. We've
followed the BOL instructions for moving system databases but the
Alter script for the resource database fails as the resource database
doesnt exist in sysdatabases. I've tried simply moving the resource
files to the new location but then sql wont start as it cant find the
files.
Anybody have any ideas how to resolve this issue?
Thanks
MichaelThe instructions in Books Online for moving the master and resource database
files should work. However, we made some corrections to the procedure in
April 2006. If you don't have the latest version of Books Online, you might
be running into a problem.
I suggest that you download the latest version fo BOL (see the link in my
signature) and then starting with step 7 (Start the instance of SQL Server
in master-only recovery mode...), see if you can get the resource database
moved. If you still run into trouble, please report the exact error
message you're getting.
Regards,
Gail
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Download the latest version of Books Online from
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
"Michael" <michael@.hampel.fsnet.co.uk> wrote in message
news:1183985960.779841.257510@.k79g2000hse.googlegroups.com...
> We have a sql 2005 installation that has service pack 2 applied. All
> the system databases apart from the resource database have been moved
> from the default data directory to our own data directory on a
> seperate drive and this went ok. We've done this basically to make the
> back up process more efficient in our environment. The issue is that
> we cant find a way to move the resource database to the new location
> and this I beleive needs to be kept with the master database. We've
> followed the BOL instructions for moving system databases but the
> Alter script for the resource database fails as the resource database
> doesnt exist in sysdatabases. I've tried simply moving the resource
> files to the new location but then sql wont start as it cant find the
> files.
> Anybody have any ideas how to resolve this issue?
> Thanks
> Michael
>sql

Move tempdb files to a new disk

I have done a new installation which is up and running.
However the disk on which the tempdb mdf and ldf files are
is giving a problem. Is there a way to move the files to a
different disk? I know we can't detach and attach it.
Alter database does not allow the primary data file to be
deleted.
I can create a new data file on the other disk and stop
the existing datafile from growing. This will effectively
move all tempdb activity to the new disk. But is there no
better way to move the mdf and ldf files to the new disk?
TIA,
JackINF: Moving SQL Server Databases to a New Location with Detach/Attach
http://support.microsoft.com/defaul...1&Product=sql2k
Scroll down to the bottom and find the section titled 'Moving Tempdb'
You are correct in that Detach/Attach doesn't work on TempDB. This KB
article does explain the proper way to move TempDB.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Jack" <jacka8@.excite.com> wrote in message
news:e4a401c40ba6$b1358d50$a301280a@.phx.gbl...
> I have done a new installation which is up and running.
> However the disk on which the tempdb mdf and ldf files are
> is giving a problem. Is there a way to move the files to a
> different disk? I know we can't detach and attach it.
> Alter database does not allow the primary data file to be
> deleted.
> I can create a new data file on the other disk and stop
> the existing datafile from growing. This will effectively
> move all tempdb activity to the new disk. But is there no
> better way to move the mdf and ldf files to the new disk?
> TIA,
> Jack|||You do this using ALTER DATABASE. See KB 224071 for more info.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Jack" <jacka8@.excite.com> wrote in message
news:e4a401c40ba6$b1358d50$a301280a@.phx.gbl...
> I have done a new installation which is up and running.
> However the disk on which the tempdb mdf and ldf files are
> is giving a problem. Is there a way to move the files to a
> different disk? I know we can't detach and attach it.
> Alter database does not allow the primary data file to be
> deleted.
> I can create a new data file on the other disk and stop
> the existing datafile from growing. This will effectively
> move all tempdb activity to the new disk. But is there no
> better way to move the mdf and ldf files to the new disk?
> TIA,
> Jack|||Hi,
How to Move TEMPDB from one location to another
---
USE master
go
ALTER DATABASE tempdb MODIFY FILE (NAME = tempdev, FILENAME =
'E:\tempdb.mdf')
go
ALTER DATABASE tempdb MODIFY FILE (NAME = templog, FILENAME =
'E:\templog.ldf')
go
where NAME refers to the logical name of the tempdb database and
log files, and where FILENAME refers to the new location of the
tempdb files. Once this command has run, you must restart the
mssqlserver service before it takes affect.
This steps are common for SQL Server 7.0 and 2000.
Thanks
Hari
MCDBA
"Jack" <jacka8@.excite.com> wrote in message
news:e4a401c40ba6$b1358d50$a301280a@.phx.gbl...
> I have done a new installation which is up and running.
> However the disk on which the tempdb mdf and ldf files are
> is giving a problem. Is there a way to move the files to a
> different disk? I know we can't detach and attach it.
> Alter database does not allow the primary data file to be
> deleted.
> I can create a new data file on the other disk and stop
> the existing datafile from growing. This will effectively
> move all tempdb activity to the new disk. But is there no
> better way to move the mdf and ldf files to the new disk?
> TIA,
> Jack

Move SQL Database

i am not a sql programmer, but I need to move two "user databases" in a sql
2005 express installation from one drive to another.
This article explains what I need but it says I need to run some commands,
but not where to type the command or run them.
http://support.microsoft.com/kb/224071
Anyway can I just detach, move the data and log file and then reatach it
using the SQL Server Management Studio Express?
ThanksHi
The commands should be run from a SQLCMD prompt at the command line.
If SSMSE is the same as SSMS then you can right click the database node
choose all tasks and then attach from the menus.
John
"frm3389" wrote:
> i am not a sql programmer, but I need to move two "user databases" in a sql
> 2005 express installation from one drive to another.
> This article explains what I need but it says I need to run some commands,
> but not where to type the command or run them.
> http://support.microsoft.com/kb/224071
> Anyway can I just detach, move the data and log file and then reatach it
> using the SQL Server Management Studio Express?
> Thanks|||Absolutely! Go that way if you don't wanna bother yourself with those code
pieces.
Warning:
It those databases are in a production environment, to prevent any data
loss, you may want to change your databases "Restrict Access" property to
SINGLE_USER (from database options) and then do not forget to set it back to
MULTI_USER to avoid any possible chaos :)
--
Ekrem Ã?nsoy
"frm3389" <frm3389@.discussions.microsoft.com> wrote in message
news:14312EB2-50D5-447B-895E-DD861F80AD24@.microsoft.com...
>i am not a sql programmer, but I need to move two "user databases" in a sql
> 2005 express installation from one drive to another.
> This article explains what I need but it says I need to run some commands,
> but not where to type the command or run them.
> http://support.microsoft.com/kb/224071
> Anyway can I just detach, move the data and log file and then reatach it
> using the SQL Server Management Studio Express?
> Thanks|||Thanks for the added advice. That is what I needed.

Move Reporting Services Web Installation to another Web Server

Move Reporting Services Web Installation to another Web ServerI assume this is RS 2000. You may want to check this KB article (in
particular the second section of the article):
http://support.microsoft.com/default.aspx?scid=842425
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Ennamorato" <PaulEnnamorato@.discussions.microsoft.com> wrote in
message news:2C6E33F4-A377-4803-9A8B-B46CBE7E5662@.microsoft.com...
>

Move Log File Locations

I am trying to split the log and data files between two drives on a new
SQL-Server 2000 installation. I followed the instructions from the MS
article 224071 (Moving SQL Server databases to a new location with
Detach/Attach).

Unfortunalty, when I try to move the Master database, as per
instructions, access to SQL-Sever is lost;the service will never start
again. I've tried this twice after re-installing with the same results.

Anyone have any ideas as to what is going wrong?

TimDon't move the master database and log file. There is so little
activity in master that you will not gain one iota of benefit from
splitting the data and log file locations.

I am willing to bet you could put the master log file on a floppy disk
and you wouldn't notice a performance difference. The only thing read
from master (from a user perspective) is login information. Since
changes are rarely made in master, you'll get nothing from moving the
log to a separate device.|||This isn't a performance issue. We want all logs in a single directory,
and all data in a single directory (as well as separate drives) for
standardization. Performance issues related to production and tempdb
databases are the other reason.

Anyone else care to offer a solution?

Tim

joshsackett wrote:
> Don't move the master database and log file. There is so little
> activity in master that you will not gain one iota of benefit from
> splitting the data and log file locations.
> I am willing to bet you could put the master log file on a floppy
disk
> and you wouldn't notice a performance difference. The only thing read
> from master (from a user perspective) is login information. Since
> changes are rarely made in master, you'll get nothing from moving the
> log to a separate device.|||Got it - no need for a solution now :)

tim.pascoe@.cciw.ca wrote:
> This isn't a performance issue. We want all logs in a single
directory,
> and all data in a single directory (as well as separate drives) for
> standardization. Performance issues related to production and tempdb
> databases are the other reason.
> Anyone else care to offer a solution?
> Tim
>
> joshsackett wrote:
> > Don't move the master database and log file. There is so little
> > activity in master that you will not gain one iota of benefit from
> > splitting the data and log file locations.
> > I am willing to bet you could put the master log file on a floppy
> disk
> > and you wouldn't notice a performance difference. The only thing
read
> > from master (from a user perspective) is login information. Since
> > changes are rarely made in master, you'll get nothing from moving
the
> > log to a separate device.