Rebuild master db

I've recently had to rebuild the master database using the rebuild -m
utility. However, i've noticed some strange behaviours in my application
since in particular that a few errors are mssing from the sysmessages table.
What would be the preferred plan of action from here to get the system
tables back to a similar state before the rebuild ( I don't have a usable
backup of the master database i'm afraid)? Would it be to reapply the latest
SP?
I'm using SQL2k on a win2k box and prior to the rebuild of master, it was
patched up to SP3.
Thanks
RichYes, it is probable that a service pack adds rows to sysmessages. Do you
know the error number of the missing rows?
Another alternative is that you, or your application added those rows.
Error number < 50000 should mean they were added by SQL Server (service pack
is likely), > 50000 mean application.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Rich" <richbrownesq@.hotmail.com> wrote in message
news:%23UwsY15pDHA.744@.tk2msftngp13.phx.gbl...
> I've recently had to rebuild the master database using the rebuild -m
> utility. However, i've noticed some strange behaviours in my application
> since in particular that a few errors are mssing from the sysmessages
table.
> What would be the preferred plan of action from here to get the system
> tables back to a similar state before the rebuild ( I don't have a usable
> backup of the master database i'm afraid)? Would it be to reapply the
latest
> SP?
> I'm using SQL2k on a win2k box and prior to the rebuild of master, it was
> patched up to SP3.
> Thanks
> Rich
>|||There's 25 missing errors, ids ranging from 1960 -> 21520 and I think most
of these are sql server errors.
Would you recommend reapplying the SP or could i just insert the missing
rows? The issue i have with this is that there could be other modifications
to the system databases that i'm unaware of and wouldn't be fixed without
the latest SP.
However, when i run select serverproperty('productlevel'), it tells me SP3
is installed. Do you know if this will prevent me installing it again?
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:OeoPM75pDHA.4004@.TK2MSFTNGP11.phx.gbl...
> Yes, it is probable that a service pack adds rows to sysmessages. Do you
> know the error number of the missing rows?
> Another alternative is that you, or your application added those rows.
> Error number < 50000 should mean they were added by SQL Server (service
pack
> is likely), > 50000 mean application.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Rich" <richbrownesq@.hotmail.com> wrote in message
> news:%23UwsY15pDHA.744@.tk2msftngp13.phx.gbl...
> > I've recently had to rebuild the master database using the rebuild -m
> > utility. However, i've noticed some strange behaviours in my application
> > since in particular that a few errors are mssing from the sysmessages
> table.
> > What would be the preferred plan of action from here to get the system
> > tables back to a similar state before the rebuild ( I don't have a
usable
> > backup of the master database i'm afraid)? Would it be to reapply the
> latest
> > SP?
> >
> > I'm using SQL2k on a win2k box and prior to the rebuild of master, it
was
> > patched up to SP3.
> >
> > Thanks
> > Rich
> >
> >
>|||Yes, you should reapply the service pack. You are correct in other things
can be affected by the service pack, like bug fixes in system stored
procedures etc. The reason why you get sp3 is probably because the function
checks the .exe file and that didn't change because of your rebuild. I did a
search in the archives and came across below, amongst others (strange that I
did not find anything in BOL or KB that you need to reapply service pack).
http://tinyurl.com/ue4s
Or full URL:
http://groups.google.com/groups?q=rebuildm+%22service+pack%22+group:microsoft.public.sqlserver.*&hl=en&lr=&ie=UTF-8&group=microsoft.public.sqlserver.*&selm=4oheDoLQDHA.1724%40cpmsftngxa09.phx.gbl&rnum=5
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Rich" <richbrownesq@.hotmail.com> wrote in message
news:%234QgaA6pDHA.1672@.TK2MSFTNGP09.phx.gbl...
> There's 25 missing errors, ids ranging from 1960 -> 21520 and I think most
> of these are sql server errors.
> Would you recommend reapplying the SP or could i just insert the missing
> rows? The issue i have with this is that there could be other
modifications
> to the system databases that i'm unaware of and wouldn't be fixed without
> the latest SP.
> However, when i run select serverproperty('productlevel'), it tells me SP3
> is installed. Do you know if this will prevent me installing it again?
>
> "Tibor Karaszi"
<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
> wrote in message news:OeoPM75pDHA.4004@.TK2MSFTNGP11.phx.gbl...
> > Yes, it is probable that a service pack adds rows to sysmessages. Do you
> > know the error number of the missing rows?
> >
> > Another alternative is that you, or your application added those rows.
> >
> > Error number < 50000 should mean they were added by SQL Server (service
> pack
> > is likely), > 50000 mean application.
> > --
> > Tibor Karaszi, SQL Server MVP
> > Archive at:
> >
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> > "Rich" <richbrownesq@.hotmail.com> wrote in message
> > news:%23UwsY15pDHA.744@.tk2msftngp13.phx.gbl...
> > > I've recently had to rebuild the master database using the rebuild -m
> > > utility. However, i've noticed some strange behaviours in my
application
> > > since in particular that a few errors are mssing from the sysmessages
> > table.
> > > What would be the preferred plan of action from here to get the system
> > > tables back to a similar state before the rebuild ( I don't have a
> usable
> > > backup of the master database i'm afraid)? Would it be to reapply the
> > latest
> > > SP?
> > >
> > > I'm using SQL2k on a win2k box and prior to the rebuild of master, it
> was
> > > patched up to SP3.
> > >
> > > Thanks
> > > Rich
> > >
> > >
> >
> >
>sql