Rename Server - SQL 2005 RS

Windows 2003 R2, SQL 2005
I use Virtual Server images for my testing environments and so I need to be
able to take my master copy of an image and rename the server so that I can
put out on the network. When I do this, Reporting Services is unable to
connect to the database, which is no surprise really. I'm having trouble
finding info on how to fix this.
Anyone know what's involved with getting reporting services to work if you
rename the server?
--
thanks,
-JeffHave you tried using the Reporting Services Configuration Utility? This
tool lets' you point to the correct server.
--
Shaun Beane, MCT, MCDST, MCDBA
dbageek.blogspot.com
"Jefffff" <Jefffff@.discussions.microsoft.com> wrote in message
news:6E591CBD-F70B-4F50-B289-5EDF4BDB6D1B@.microsoft.com...
> Windows 2003 R2, SQL 2005
> I use Virtual Server images for my testing environments and so I need to
> be
> able to take my master copy of an image and rename the server so that I
> can
> put out on the network. When I do this, Reporting Services is unable to
> connect to the database, which is no surprise really. I'm having trouble
> finding info on how to fix this.
> Anyone know what's involved with getting reporting services to work if you
> rename the server?
> --
> thanks,
> -Jeff|||Many moons later, I've found some time to test this...
What I find is that after renaming the server, the Configuration Utility
doesn't work. When you launch it, you need to first connect to an instance
of Reporting Services, before you can configure anything, and after renaming
the server, you cannot connect to the Reporting Services instance on that
server, therefore you cannot configure anything.
Unless I'm missing something, it seems renaming your server means
reinstalling SRS.
I'm not sure how the utility connects to an SRS instance. If I had the time
to figure that out, maybe I could figure out a fix.
Anyone else out there dealing with this one?
--
thanks,
-Jeff
"Shaun Beane" wrote:
> Have you tried using the Reporting Services Configuration Utility? This
> tool lets' you point to the correct server.
> --
> Shaun Beane, MCT, MCDST, MCDBA
> dbageek.blogspot.com
> "Jefffff" <Jefffff@.discussions.microsoft.com> wrote in message
> news:6E591CBD-F70B-4F50-B289-5EDF4BDB6D1B@.microsoft.com...
> > Windows 2003 R2, SQL 2005
> >
> > I use Virtual Server images for my testing environments and so I need to
> > be
> > able to take my master copy of an image and rename the server so that I
> > can
> > put out on the network. When I do this, Reporting Services is unable to
> > connect to the database, which is no surprise really. I'm having trouble
> > finding info on how to fix this.
> >
> > Anyone know what's involved with getting reporting services to work if you
> > rename the server?
> >
> > --
> > thanks,
> > -Jeff
>
>

removing replication on SP

I have my own SP in the master database that had sp_MS_marksystemobject applied to it. It now needs revising but it cannot be renamed. It cannot be dropped because it is used for replication (apparently).
When I try to drop it, get message: Server: Msg 3724, Level 16, State 2, Line 1
Cannot drop the procedure '<sp_name>' because it is being used for replication.
Anyone know how the replication can be removed
use sp_MSunmarkreplinfo against this proc and then drop it from within isqlw.

Removing Databases

Using SQL Server Management Studio, I see 4 entries, master, model, msdb and temdb, under Databases -> System Databases. Which of these can I safely remove, if any?

Thank you

Hi there,

I don't think you should remove any of them....Each of the system databases is there for a purpose and removing one or more will adversely affect your database server (possibly to the point of inoperability).

Below is a link to adescription of the purpose of each system database:
System Databases

Hope that helps a bit or sheds some light on the matter, but sorry if it doesn't
|||Why should one delete the system databases ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Nate,

Thank you for the reponse, it helped quite a bit. I am new to SQL Express and I wasn't sure what those Db's were for, so the link is very helpful.