How to determine what patches are needed to restore Master

I have had to rebuild our SQL server from scratch due to hardware failure.
Because of a version mismatch... this has presented a problem to me in
restoring the Master database. The previous admin did not leave notes on
what patches were installed on the server, and all that I know is SP1 was
installed minimum.
I have since installed SP1, but I seem to be missing a couple more patches.
Is there any way to determine what patches I need from the error message
given during restore? Current version: 134218112 Master Database
Version: 134218262
Thank you all in advance for your assistance.Was able to extract the actual software version information...
The current software version is: 8.00.384
The backup Master version is : 8.00.534

how to detach master db

Hi,
how do I detach master db?
what are the steps?What for?
AMB
"Britney" wrote:

> Hi,
> how do I detach master db?
> what are the steps?
>
>|||Hi Britney,
Look at this thread for common detaching.
http://groups.google.de/groups?q=ti...phx.gbl&rnum=1
But most of them wont work with the master db. Wonder why you want to
attach / detach the master db ?
HTH, Jens Smeyer.
http://www.sqlserver2005.de
--
"Britney" <britneychen_2001@.yahoo.com> schrieb im Newsbeitrag
news:uLDsr1ERFHA.904@.tk2msftngp13.phx.gbl...
> Hi,
> how do I detach master db?
> what are the steps?
>|||all I want to ask is if it's possible to do so.
"Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:enPchDFRFHA.1416@.TK2MSFTNGP10.phx.gbl...
> Hi Britney,
> Look at this thread for common detaching.
>
http://groups.google.de/groups?q=ti...phx.gbl&rnum=1
> But most of them wont work with the master db. Wonder why you want to
> attach / detach the master db ?
> HTH, Jens Smeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Britney" <britneychen_2001@.yahoo.com> schrieb im Newsbeitrag
> news:uLDsr1ERFHA.904@.tk2msftngp13.phx.gbl...
>|||You have to change the start paramters for the SQL Server to do so:
-dD:\MSSQL7\data\master.mdf <--
-eD:\MSSQL7\log\ErrorLog
-lD:\MSSQL7\data\mastlog.ldf <--
for more details look here:
rl]
HTH, Jens Suessmeyer.
[url]http://www.sqlserver2005.de" target="_blank">http://support.microsoft.com/Defaul...qlserver2005.de
--
"Britney" <britneychen_2001@.yahoo.com> schrieb im Newsbeitrag
news:%23Cdc6LFRFHA.612@.TK2MSFTNGP14.phx.gbl...
> all I want to ask is if it's possible to do so.
> "Jens Smeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in
> message news:enPchDFRFHA.1416@.TK2MSFTNGP10.phx.gbl...
> http://groups.google.de/groups?q=ti...phx.gbl&rnum=1
>

How to Deploy Reports to a Production Environment

Our situation is that we are developing a set of "master" reports locally
using Visual Studio .NET 2003 (and, of course, the Reporting Services
designer). Once the master reports are finished, we will need to install
these reports to our customers' computers (their computers are not a part of
our network, we don't have access to them to deploy from our computers and
the Visual Studio .NET 2003 solution/project). And then we will need to
deploy to the ReportServer on their server.
Additionally, the customers' server will have VB .NET installed (the basic
edition to allow RDL development).
So, should we simply copy the solution, project, RDS, and RDL files to the
customers' server, then open the solution in VB .NET, and deploy? Or is
there a better way?
Also, since we are developing the master reports in a solution/project in
Visual Studio .NET on our local development servers, is there any
compatibility issues in trying to open that same solution in VB .NET on the
customers' server?
Thanks.I would think the easiest way would be to build a quick app to do this using
the CreateReport SOAP Api. You could then make this app as simple or
complex as you need it and not need to worry about your customers having any
VS components. We shipped a sample app (RSExplorer I believe) that does
allow you to deploy but it would have to be modified if you wanted to easily
upload a directory of rdls.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Belak" <nospam@.nospam.com> wrote in message
news:OrhITzzmEHA.3264@.TK2MSFTNGP12.phx.gbl...
> Our situation is that we are developing a set of "master" reports locally
> using Visual Studio .NET 2003 (and, of course, the Reporting Services
> designer). Once the master reports are finished, we will need to install
> these reports to our customers' computers (their computers are not a part
of
> our network, we don't have access to them to deploy from our computers and
> the Visual Studio .NET 2003 solution/project). And then we will need to
> deploy to the ReportServer on their server.
> Additionally, the customers' server will have VB .NET installed (the basic
> edition to allow RDL development).
> So, should we simply copy the solution, project, RDS, and RDL files to the
> customers' server, then open the solution in VB .NET, and deploy? Or is
> there a better way?
> Also, since we are developing the master reports in a solution/project in
> Visual Studio .NET on our local development servers, is there any
> compatibility issues in trying to open that same solution in VB .NET on
the
> customers' server?
> Thanks.
>

How to delete a sqlserver system stored procedure in master?

Hi,
I need to replace a sqlserver system stored procedure
(sp_depends) because of a bug in the master database. But
it doesn't allow me to delete it. What steps do I need
to follow to delete a system stored procedure?
Thx"Tony" <indengr@.yahoo.com> wrote in message
news:087901c38391$a55abe30$a101280a@.phx.gbl...
> I need to replace a sqlserver system stored procedure
> (sp_depends) because of a bug in the master database. But
> it doesn't allow me to delete it. What steps do I need
> to follow to delete a system stored procedure?
Which bug, can you document that for us? Providing you are a sysadmin you
should be able to use ALTER PROC to modify a system stored procedure. As I'm
sure you're aware, making revisions like this place you in unsupported
territory,
Steve|||here is the bug:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;180490
I'm getting this error in the sqlserver log. So I had to
replace the sp_depends procedure. I can't rename or
delete the procedure. I administer the database.
>--Original Message--
>"Tony" <indengr@.yahoo.com> wrote in message
>news:087901c38391$a55abe30$a101280a@.phx.gbl...
>> I need to replace a sqlserver system stored procedure
>> (sp_depends) because of a bug in the master database.
But
>> it doesn't allow me to delete it. What steps do I need
>> to follow to delete a system stored procedure?
>Which bug, can you document that for us? Providing you
are a sysadmin you
>should be able to use ALTER PROC to modify a system
stored procedure. As I'm
>sure you're aware, making revisions like this place you
in unsupported
>territory,
>Steve
>
>.
>|||The article you refer recommends doing just that -- creating a NEW procedure
called sp_depends2 and using that instead of sp_depends. It does not say to
delete sp_depends.
The Enterprise Manager has an extra layer of security that does not allow
you to drop any objects marked as system objects.
What error are you getting in the log?
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"tony" <indengr@.yahoo.com> wrote in message
news:099f01c383a5$7a5c7cf0$a301280a@.phx.gbl...
> here is the bug:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;180490
> I'm getting this error in the sqlserver log. So I had to
> replace the sp_depends procedure. I can't rename or
> delete the procedure. I administer the database.
>
>
> >--Original Message--
> >"Tony" <indengr@.yahoo.com> wrote in message
> >news:087901c38391$a55abe30$a101280a@.phx.gbl...
> >> I need to replace a sqlserver system stored procedure
> >> (sp_depends) because of a bug in the master database.
> But
> >> it doesn't allow me to delete it. What steps do I need
> >> to follow to delete a system stored procedure?
> >
> >Which bug, can you document that for us? Providing you
> are a sysadmin you
> >should be able to use ALTER PROC to modify a system
> stored procedure. As I'm
> >sure you're aware, making revisions like this place you
> in unsupported
> >territory,
> >
> >Steve
> >
> >
> >
> >.
> >|||I don't think whatever you are trying to do is worth the effort.
Both sp_depends and sp_depends2 rely on the sysdepends table, which is for
all practical purposes not dependable (particularly for stored procedures).
Thee is no supported utility to verify whether sysdepends table is good and
there is no supported utility to correct whatever inconsistencies or add
missing information.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"tony" <indengr@.yahoo.com> wrote in message
news:099f01c383a5$7a5c7cf0$a301280a@.phx.gbl...
> here is the bug:
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;180490
> I'm getting this error in the sqlserver log. So I had to
> replace the sp_depends procedure. I can't rename or
> delete the procedure. I administer the database.
>
>
> >--Original Message--
> >"Tony" <indengr@.yahoo.com> wrote in message
> >news:087901c38391$a55abe30$a101280a@.phx.gbl...
> >> I need to replace a sqlserver system stored procedure
> >> (sp_depends) because of a bug in the master database.
> But
> >> it doesn't allow me to delete it. What steps do I need
> >> to follow to delete a system stored procedure?
> >
> >Which bug, can you document that for us? Providing you
> are a sysadmin you
> >should be able to use ALTER PROC to modify a system
> stored procedure. As I'm
> >sure you're aware, making revisions like this place you
> in unsupported
> >territory,
> >
> >Steve
> >
> >
> >
> >.
> >|||You should be write your own stored procedure
>--Original Message--
>Hi,
> I need to replace a sqlserver system stored procedure
>(sp_depends) because of a bug in the master database.
But
>it doesn't allow me to delete it. What steps do I need
>to follow to delete a system stored procedure?
>Thx
>.
>