Moving the Reprot Server log files in 2005

I have just setup a SQL Server 2005 instance and am seperating the log files
on a seperate drive. Can the ReportServer and ReportServerTempDB log files be
moved just like any user database or are there special instructions for
moving the log file of these two databases? I have searched the MS Knowledge
Base and could only find an article about moving the entire RS databases to a
new server.
Any help would be appreciated.
Hi
"MACason" wrote:

> I have just setup a SQL Server 2005 instance and am seperating the log files
> on a seperate drive. Can the ReportServer and ReportServerTempDB log files be
> moved just like any user database or are there special instructions for
> moving the log file of these two databases? I have searched the MS Knowledge
> Base and could only find an article about moving the entire RS databases to a
> new server.
> Any help would be appreciated.
You should be able to move the location of the database log files like any
other database. You would need to stop Reporting Services before doing so.
John

Moving the Reprot Server log files in 2005

I have just setup a SQL Server 2005 instance and am seperating the log files
on a seperate drive. Can the ReportServer and ReportServerTempDB log files b
e
moved just like any user database or are there special instructions for
moving the log file of these two databases? I have searched the MS Knowledge
Base and could only find an article about moving the entire RS databases to
a
new server.
Any help would be appreciated.Hi
"MACason" wrote:

> I have just setup a SQL Server 2005 instance and am seperating the log fil
es
> on a seperate drive. Can the ReportServer and ReportServerTempDB log files
be
> moved just like any user database or are there special instructions for
> moving the log file of these two databases? I have searched the MS Knowled
ge
> Base and could only find an article about moving the entire RS databases t
o a
> new server.
> Any help would be appreciated.
You should be able to move the location of the database log files like any
other database. You would need to stop Reporting Services before doing so.
John

Moving SQL2k to new appliance

I am moving a SQL 2k database from a Windows 2000 server to a Windows 2003 server (seperate appliances) and would like as little SQL downtime as possible.

I have several applications that I believe are connecting to servernow by servernow’s name and don’t want to have to figure out how to change them to servernew.Would it work if I built servernew and copied/moved the SQL database to servernew, then take servernow off line and change servernew’s name to servernow?

I am open to any suggestions on other more appropriate methods.

Thanks in advance

Melonheads Sister

That suggestions should work. Ensure you follow the instructions at http://msdn2.microsoft.com/en-us/library/ms143799.aspx for renaming the server. Ensure you move over the logins.

Thanks,

Peter Saddow

|||

Hi,

i would suggest to refer http://vyaskn.tripod.com/moving_sql_server.htm for Moving SQL Server complete idea.

Hemantgiri S. Goswami

|||

Thank you both. Looks like both documents will be very useful.

Melonheads Sister

Moving Report Server Log Files

I am setting up a new SQL Server 2005 EE server with Reprting Services
installed. The log files have all been moved to a seperate drive. However, I
have never moved log files for Reporting Services and can find no
documentation for this procedure. Is there anything unique about moving the
ReportServer_log.LDF and ReportServerTempDB_log.LDF or can they be moved just
like a normal user database?
Thanks,
Mike C.
I haven't done this myself, but I'd be *very* surprised if RS cares about the physical location of
the database files. That would be a really crappy idea, if it did.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:EADD349C-1278-480E-B5AD-17E33A18BCB8@.microsoft.com...
>I am setting up a new SQL Server 2005 EE server with Reprting Services
> installed. The log files have all been moved to a seperate drive. However, I
> have never moved log files for Reporting Services and can find no
> documentation for this procedure. Is there anything unique about moving the
> ReportServer_log.LDF and ReportServerTempDB_log.LDF or can they be moved just
> like a normal user database?
> Thanks,
> Mike C.

Moving Report Server Log Files

I am setting up a new SQL Server 2005 EE server with Reprting Services
installed. The log files have all been moved to a seperate drive. However, I
have never moved log files for Reporting Services and can find no
documentation for this procedure. Is there anything unique about moving the
ReportServer_log.LDF and ReportServerTempDB_log.LDF or can they be moved just
like a normal user database?
Thanks,
Mike C.I haven't done this myself, but I'd be *very* surprised if RS cares about the physical location of
the database files. That would be a really crappy idea, if it did.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:EADD349C-1278-480E-B5AD-17E33A18BCB8@.microsoft.com...
>I am setting up a new SQL Server 2005 EE server with Reprting Services
> installed. The log files have all been moved to a seperate drive. However, I
> have never moved log files for Reporting Services and can find no
> documentation for this procedure. Is there anything unique about moving the
> ReportServer_log.LDF and ReportServerTempDB_log.LDF or can they be moved just
> like a normal user database?
> Thanks,
> Mike C.

Moving Report Server Log Files

I am setting up a new SQL Server 2005 EE server with Reprting Services
installed. The log files have all been moved to a seperate drive. However, I
have never moved log files for Reporting Services and can find no
documentation for this procedure. Is there anything unique about moving the
ReportServer_log.LDF and ReportServerTempDB_log.LDF or can they be moved jus
t
like a normal user database?
Thanks,
Mike C.I haven't done this myself, but I'd be *very* surprised if RS cares about th
e physical location of
the database files. That would be a really crappy idea, if it did.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:EADD349C-1278-480E-B5AD-17E33A18BCB8@.microsoft.com...
>I am setting up a new SQL Server 2005 EE server with Reprting Services
> installed. The log files have all been moved to a seperate drive. However,
I
> have never moved log files for Reporting Services and can find no
> documentation for this procedure. Is there anything unique about moving th
e
> ReportServer_log.LDF and ReportServerTempDB_log.LDF or can they be moved j
ust
> like a normal user database?
> Thanks,
> Mike C.

Moving Replication Distributor/Publisher

I have an SQL Server 2k box set as a publisher/distributor with several
publications. Each publication has two subscriptions each to seperate
sql 2k servers. I need to move the existings replicated databases from
the current publisher/distributor to a new SQL 2k5 Server that will act
as the new publisher/distributor for the existing publications. All
replication strategies are using merge replication.
Current setup:
Server A (win svr 2000, sql 2k, pub/dist, merge repli)
|
database
|
________ publication _______
| |
subscription B subscription c
| |
| |
Server B (subscriber, sql 2k) Server C (subscriber, sql 2k)
Server D (win svr 2003, sql 2k5, pub/dis, merge repli)
Need to replace Server A with Server D
Does anyone have a decent process for this. Since I am not doing
anything to the subscriber databases, I shouldn't have anything to do
at the distant end? I can't replicate from 2k to 2k5 so it looks like
I would need downtime to move/copy database exactly from server A to
server D. If I cancel the subscriptions from the SQL 2k server, will I
have a problem with the subscribers accepting the new subscriptions
from the new distributor/publisher?
Tks for any help,
TonyYour best approach is to run the agents one last time, queisce the systems,
script out the subscriptions and publications, drop them, and then run them
on server d.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tony" <tony.otis@.gmail.com> wrote in message
news:1149271877.583934.41800@.i39g2000cwa.googlegroups.com...
>I have an SQL Server 2k box set as a publisher/distributor with several
> publications. Each publication has two subscriptions each to seperate
> sql 2k servers. I need to move the existings replicated databases from
> the current publisher/distributor to a new SQL 2k5 Server that will act
> as the new publisher/distributor for the existing publications. All
> replication strategies are using merge replication.
> Current setup:
> Server A (win svr 2000, sql 2k, pub/dist, merge repli)
> |
> database
> |
> ________ publication _______
> | |
> subscription B subscription c
> | |
> | |
> Server B (subscriber, sql 2k) Server C (subscriber, sql 2k)
>
> Server D (win svr 2003, sql 2k5, pub/dis, merge repli)
> Need to replace Server A with Server D
> Does anyone have a decent process for this. Since I am not doing
> anything to the subscriber databases, I shouldn't have anything to do
> at the distant end? I can't replicate from 2k to 2k5 so it looks like
> I would need downtime to move/copy database exactly from server A to
> server D. If I cancel the subscriptions from the SQL 2k server, will I
> have a problem with the subscribers accepting the new subscriptions
> from the new distributor/publisher?
> Tks for any help,
> Tony
>|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uNrLGdphGHA.4892@.TK2MSFTNGP02.phx.gbl...
> Your best approach is to run the agents one last time, queisce the
systems,
> script out the subscriptions and publications, drop them, and then run
them
> on server d.
I will add (having done this w/o incident) that in case it's not clear, when
you subscribe on the subscribers, if you say that the subscriber already has
the schema and data you should be able to pick up where you left off w/o
incident.
Incidentally, what I've done to "speed things up" a bit is something like
the following pattern:
Full backup of databases on Server A.
Restore to D with NORECOVERY
Queisce the systems.
Transaction log backup of databases on Server A
Restore to D with RECOVERY
Rebuild replication
Start up connections to Server D.
(note, if the full backups take a long time you can insert another round of
transaction log back/restore BEFORE you queisce the systems.)
Done this way, you can effectively "move" very large databases in a very
short time (since effectively the bulk of the time is spent in the
transaction log backup/restore which should be FAR smaller than copying the
full database.) This is even more true if you've got this all scripted out
in advance.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Tony" <tony.otis@.gmail.com> wrote in message
> news:1149271877.583934.41800@.i39g2000cwa.googlegroups.com...
> >I have an SQL Server 2k box set as a publisher/distributor with several
> > publications. Each publication has two subscriptions each to seperate
> > sql 2k servers. I need to move the existings replicated databases from
> > the current publisher/distributor to a new SQL 2k5 Server that will act
> > as the new publisher/distributor for the existing publications. All
> > replication strategies are using merge replication.
> >
> > Current setup:
> > Server A (win svr 2000, sql 2k, pub/dist, merge repli)
> > |
> > database
> > |
> > ________ publication _______
> > | |
> > subscription B subscription c
> > | |
> > | |
> > Server B (subscriber, sql 2k) Server C (subscriber, sql 2k)
> >
> >
> > Server D (win svr 2003, sql 2k5, pub/dis, merge repli)
> > Need to replace Server A with Server D
> >
> > Does anyone have a decent process for this. Since I am not doing
> > anything to the subscriber databases, I shouldn't have anything to do
> > at the distant end? I can't replicate from 2k to 2k5 so it looks like
> > I would need downtime to move/copy database exactly from server A to
> > server D. If I cancel the subscriptions from the SQL 2k server, will I
> > have a problem with the subscribers accepting the new subscriptions
> > from the new distributor/publisher?
> >
> > Tks for any help,
> >
> > Tony
> >
>

Moving MastLog, msdblog and modelLog

I need to move the transaction logs for all the sql db's (including master,
model and user db's etc) to a seperate drive. Does anyone have any experience
doing this in a sql cluster?
Detach and attach method don't work on this DB
You can use KB : http://support.microsoft.com/?id=224071.
HTH
Franco Conenna [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no rights"
"Scan le Gentil" ha scritto:

> I need to move the transaction logs for all the sql db's (including master,
> model and user db's etc) to a seperate drive. Does anyone have any experience
> doing this in a sql cluster?
> Detach and attach method don't work on this DB
>
|||Thanks.
"Franco Conenna [MSFT]" wrote:
[vbcol=seagreen]
> You can use KB : http://support.microsoft.com/?id=224071.
> HTH
> Franco Conenna [MSFT]
> "This posting is provided "AS IS" with no warranties, and confers no rights"
> "Scan le Gentil" ha scritto: