No ending Rebuild master

I'm using SQL SERVER 2000 and in the process of establishing recovery
guide.
Tried to rebuild master using rebuildm.exe but the "Configuring Server"
never ending. Then I tried to copy original databases from SQLServer
Installation CD to hard disk as the "Browse for folder", but gave the
same problem. Need advice what need to be done.Hi

If you can easily recreate your logins then it may be easier just to
re-install.

You may want to try installing a second instance or testing the media on a
different server to make sure that it is not corrupt.

Make sure that orphaned users are re-associated with the logins using
sp_change_users_login.

John

"hazly" <s_hazly@.oritech.com.my> wrote in message
news:1135935740.779521.287770@.g47g2000cwa.googlegr oups.com...
> I'm using SQL SERVER 2000 and in the process of establishing recovery
> guide.
> Tried to rebuild master using rebuildm.exe but the "Configuring Server"
> never ending. Then I tried to copy original databases from SQLServer
> Installation CD to hard disk as the "Browse for folder", but gave the
> same problem. Need advice what need to be done.|||Settled the problem by changing attribute of all the files from
readonly to read-write.

No Differential Backup on Master DB

Hi, Can someone plzz explain the below reason
"Differential backups are not allowed for the master database since
they require that complete backups be applied without recovery as the
first step. When restoring the master database, restore without
recovery is not allowed."
Hi
If you look in BOL on how Master DB needs to be restored, you will notice
that it is not an easy procedure.
If Master DB gets bigger than a manageable size (say 100Mb), then you have a
serious problem. You have user objects in there and you are compromising
your recoverability of your server.
A small DB like Master needs no differential backups and not much changes in
it, and it is so quick to do a full backup, that it is not worth the effort.
Regards-
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sasiraj" <vardhansasi@.gmail.com> wrote in message
news:1131737977.922320.82800@.g14g2000cwa.googlegro ups.com...
> Hi, Can someone plzz explain the below reason
> "Differential backups are not allowed for the master database since
> they require that complete backups be applied without recovery as the
> first step. When restoring the master database, restore without
> recovery is not allowed."
>

No Differential Backup on Master DB

Hi, Can someone plzz explain the below reason
"Differential backups are not allowed for the master database since
they require that complete backups be applied without recovery as the
first step. When restoring the master database, restore without
recovery is not allowed."Hi
If you look in BOL on how Master DB needs to be restored, you will notice
that it is not an easy procedure.
If Master DB gets bigger than a manageable size (say 100Mb), then you have a
serious problem. You have user objects in there and you are compromising
your recoverability of your server.
A small DB like Master needs no differential backups and not much changes in
it, and it is so quick to do a full backup, that it is not worth the effort.
Regards-
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sasiraj" <vardhansasi@.gmail.com> wrote in message
news:1131737977.922320.82800@.g14g2000cwa.googlegroups.com...
> Hi, Can someone plzz explain the below reason
> "Differential backups are not allowed for the master database since
> they require that complete backups be applied without recovery as the
> first step. When restoring the master database, restore without
> recovery is not allowed."
>sql

No Differential Backup on Master DB

Hi, Can someone plzz explain the below reason
"Differential backups are not allowed for the master database since
they require that complete backups be applied without recovery as the
first step. When restoring the master database, restore without
recovery is not allowed."Hi
If you look in BOL on how Master DB needs to be restored, you will notice
that it is not an easy procedure.
If Master DB gets bigger than a manageable size (say 100Mb), then you have a
serious problem. You have user objects in there and you are compromising
your recoverability of your server.
A small DB like Master needs no differential backups and not much changes in
it, and it is so quick to do a full backup, that it is not worth the effort.
Regards-
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"sasiraj" <vardhansasi@.gmail.com> wrote in message
news:1131737977.922320.82800@.g14g2000cwa.googlegroups.com...
> Hi, Can someone plzz explain the below reason
> "Differential backups are not allowed for the master database since
> they require that complete backups be applied without recovery as the
> first step. When restoring the master database, restore without
> recovery is not allowed."
>

No dbo in the database!

Hi All
I have a database where there is no dbo user. There seems
to be some login mismatch that I can't fix up.
The master shows sa (in fact sa is the dbo in another db
on the same server) but sa, dbo does not appear in one of
the other databases and I can't add it.
I've checked out KB 305711 but it doesn't help.
Thanks
JIn Query Analyzer,
USE the database and issue this command:
EXEC sp_changedbowner 'sa'
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"J" <anonymous@.discussions.microsoft.com> wrote in message
news:000501c3af13$941724d0$a001280a@.phx.gbl...
> Hi All
> I have a database where there is no dbo user. There seems
> to be some login mismatch that I can't fix up.
> The master shows sa (in fact sa is the dbo in another db
> on the same server) but sa, dbo does not appear in one of
> the other databases and I can't add it.
> I've checked out KB 305711 but it doesn't help.
> Thanks
> J

No data in SYSPERFINFO table of Master DB

Has anybody run into the problem on not being able to access SQL performance
monitors. I have tracked it down to the SYSPERFINFO table not collecting any
data. I have worked with Microsoft and they have no idea why this is
happening. I reboot and everything is fine for about a week and then it just
stops...no warning...no nothing.
I have SQL2000 w/SP3a Enterprise running in a cluster. I have reregistered
and rebuilt the counters and ensured that they have been selected using the
exctrlst app.
Just curious.
RickOne thing I would check -- run sysmon with logging turned
on, gathering data every minute or so. Perhaps there's so
much activity that IT isn't collecting the data in a
timely fashion. I've seen that happen on busy systems,
but I've never corelated that with the SYSPERFINFO table.
>--Original Message--
>Has anybody run into the problem on not being able to
access SQL performance
>monitors. I have tracked it down to the SYSPERFINFO table
not collecting any
>data. I have worked with Microsoft and they have no idea
why this is
>happening. I reboot and everything is fine for about a
week and then it just
>stops...no warning...no nothing.
>I have SQL2000 w/SP3a Enterprise running in a cluster. I
have reregistered
>and rebuilt the counters and ensured that they have been
selected using the
>exctrlst app.
>Just curious.
>Rick
>
>.
>

Newly created stored procedure => master db

I have upgraded my SQLExpress to SP1 but since doing this I am not able to
create stored procedures under the database that I created. It seems as if
any new procs are created in the master database.
If I create a new proc, it is not displayed under the stored procedure
folder. Iit is displayed in the folder c:\mydocuments\SQL ServerManagement
Studio Express\Projects along with the other procs that I'd created prior to
the upgrade.
If I open the newly created proc then I'm asked to login to the SQL Express
again (I already have Management Studio Express open and logged in to my own
database). Once the proc is open , the combo box "available databases" on the
toolbar displayes, 'master'. So it seems I've logged in to the master
database where the new proc has been created. But it is not displayed in the
Stored Procs of the master either.
What has gone wrong? I should be able to create new stored procs in my
database and not in the master database.
Can someone help - thanksLisa
What is happenening if you issue?
USE mydb
GO
CREATE PROC mmmm
AS
....
"Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in message
news:430A9254-6539-4C84-8C57-DBC4E3C0AADA@.microsoft.com...
>I have upgraded my SQLExpress to SP1 but since doing this I am not able to
> create stored procedures under the database that I created. It seems as if
> any new procs are created in the master database.
> If I create a new proc, it is not displayed under the stored procedure
> folder. Iit is displayed in the folder c:\mydocuments\SQL ServerManagement
> Studio Express\Projects along with the other procs that I'd created prior
> to
> the upgrade.
> If I open the newly created proc then I'm asked to login to the SQL
> Express
> again (I already have Management Studio Express open and logged in to my
> own
> database). Once the proc is open , the combo box "available databases" on
> the
> toolbar displayes, 'master'. So it seems I've logged in to the master
> database where the new proc has been created. But it is not displayed in
> the
> Stored Procs of the master either.
> What has gone wrong? I should be able to create new stored procs in my
> database and not in the master database.
> Can someone help - thanks|||Thanks for your response. Unfortunately it makes no difference. I created the
new proc and then opened it, but the Connect to Database Engine dialog box is
displayed and I connect to the master db.
"Uri Dimant" wrote:
> Lisa
> What is happenening if you issue?
> USE mydb
> GO
> CREATE PROC mmmm
> AS
> .....
>
> "Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in message
> news:430A9254-6539-4C84-8C57-DBC4E3C0AADA@.microsoft.com...
> >I have upgraded my SQLExpress to SP1 but since doing this I am not able to
> > create stored procedures under the database that I created. It seems as if
> > any new procs are created in the master database.
> >
> > If I create a new proc, it is not displayed under the stored procedure
> > folder. Iit is displayed in the folder c:\mydocuments\SQL ServerManagement
> > Studio Express\Projects along with the other procs that I'd created prior
> > to
> > the upgrade.
> >
> > If I open the newly created proc then I'm asked to login to the SQL
> > Express
> > again (I already have Management Studio Express open and logged in to my
> > own
> > database). Once the proc is open , the combo box "available databases" on
> > the
> > toolbar displayes, 'master'. So it seems I've logged in to the master
> > database where the new proc has been created. But it is not displayed in
> > the
> > Stored Procs of the master either.
> >
> > What has gone wrong? I should be able to create new stored procs in my
> > database and not in the master database.
> > Can someone help - thanks
>
>|||Lisa
Ok, it is by default. You can change it by using
EXEC sp_defaultdb 'Lisa', 'AdventureWorks'
"Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in message
news:16DB04B0-8E9B-4C8C-88FD-F881A31AA781@.microsoft.com...
> Thanks for your response. Unfortunately it makes no difference. I created
> the
> new proc and then opened it, but the Connect to Database Engine dialog box
> is
> displayed and I connect to the master db.
>
> "Uri Dimant" wrote:
>> Lisa
>> What is happenening if you issue?
>> USE mydb
>> GO
>> CREATE PROC mmmm
>> AS
>> .....
>>
>> "Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in
>> message
>> news:430A9254-6539-4C84-8C57-DBC4E3C0AADA@.microsoft.com...
>> >I have upgraded my SQLExpress to SP1 but since doing this I am not able
>> >to
>> > create stored procedures under the database that I created. It seems as
>> > if
>> > any new procs are created in the master database.
>> >
>> > If I create a new proc, it is not displayed under the stored procedure
>> > folder. Iit is displayed in the folder c:\mydocuments\SQL
>> > ServerManagement
>> > Studio Express\Projects along with the other procs that I'd created
>> > prior
>> > to
>> > the upgrade.
>> >
>> > If I open the newly created proc then I'm asked to login to the SQL
>> > Express
>> > again (I already have Management Studio Express open and logged in to
>> > my
>> > own
>> > database). Once the proc is open , the combo box "available databases"
>> > on
>> > the
>> > toolbar displayes, 'master'. So it seems I've logged in to the master
>> > database where the new proc has been created. But it is not displayed
>> > in
>> > the
>> > Stored Procs of the master either.
>> >
>> > What has gone wrong? I should be able to create new stored procs in my
>> > database and not in the master database.
>> > Can someone help - thanks
>>|||Uri
I don't want to seem ignorant but where do I use this. I'm using Access as
my front end and SQLExpress as the backend. :(
Also - I'm not able to modify any of the previous stored procs. If I make a
modification and save by overwriting the proc, the changes are not there when
I open the proc again.
"Uri Dimant" wrote:
> Lisa
> Ok, it is by default. You can change it by using
> EXEC sp_defaultdb 'Lisa', 'AdventureWorks'
> "Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in message
> news:16DB04B0-8E9B-4C8C-88FD-F881A31AA781@.microsoft.com...
> > Thanks for your response. Unfortunately it makes no difference. I created
> > the
> > new proc and then opened it, but the Connect to Database Engine dialog box
> > is
> > displayed and I connect to the master db.
> >
> >
> > "Uri Dimant" wrote:
> >
> >> Lisa
> >> What is happenening if you issue?
> >> USE mydb
> >> GO
> >> CREATE PROC mmmm
> >> AS
> >> .....
> >>
> >>
> >> "Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in
> >> message
> >> news:430A9254-6539-4C84-8C57-DBC4E3C0AADA@.microsoft.com...
> >> >I have upgraded my SQLExpress to SP1 but since doing this I am not able
> >> >to
> >> > create stored procedures under the database that I created. It seems as
> >> > if
> >> > any new procs are created in the master database.
> >> >
> >> > If I create a new proc, it is not displayed under the stored procedure
> >> > folder. Iit is displayed in the folder c:\mydocuments\SQL
> >> > ServerManagement
> >> > Studio Express\Projects along with the other procs that I'd created
> >> > prior
> >> > to
> >> > the upgrade.
> >> >
> >> > If I open the newly created proc then I'm asked to login to the SQL
> >> > Express
> >> > again (I already have Management Studio Express open and logged in to
> >> > my
> >> > own
> >> > database). Once the proc is open , the combo box "available databases"
> >> > on
> >> > the
> >> > toolbar displayes, 'master'. So it seems I've logged in to the master
> >> > database where the new proc has been created. But it is not displayed
> >> > in
> >> > the
> >> > Stored Procs of the master either.
> >> >
> >> > What has gone wrong? I should be able to create new stored procs in my
> >> > database and not in the master database.
> >> > Can someone help - thanks
> >>
> >>
> >>
>
>

Newly created stored procedure => master db

I have upgraded my SQLExpress to SP1 but since doing this I am not able to
create stored procedures under the database that I created. It seems as if
any new procs are created in the master database.
If I create a new proc, it is not displayed under the stored procedure
folder. Iit is displayed in the folder c:\mydocuments\SQL ServerManagement
Studio Express\Projects along with the other procs that I'd created prior to
the upgrade.
If I open the newly created proc then I'm asked to login to the SQL Express
again (I already have Management Studio Express open and logged in to my own
database). Once the proc is open , the combo box "available databases" on th
e
toolbar displayes, 'master'. So it seems I've logged in to the master
database where the new proc has been created. But it is not displayed in the
Stored Procs of the master either.
What has gone wrong? I should be able to create new stored procs in my
database and not in the master database.
Can someone help - thanksLisa
What is happenening if you issue?
USE mydb
GO
CREATE PROC mmmm
AS
....
"Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in message
news:430A9254-6539-4C84-8C57-DBC4E3C0AADA@.microsoft.com...
>I have upgraded my SQLExpress to SP1 but since doing this I am not able to
> create stored procedures under the database that I created. It seems as if
> any new procs are created in the master database.
> If I create a new proc, it is not displayed under the stored procedure
> folder. Iit is displayed in the folder c:\mydocuments\SQL ServerManagement
> Studio Express\Projects along with the other procs that I'd created prior
> to
> the upgrade.
> If I open the newly created proc then I'm asked to login to the SQL
> Express
> again (I already have Management Studio Express open and logged in to my
> own
> database). Once the proc is open , the combo box "available databases" on
> the
> toolbar displayes, 'master'. So it seems I've logged in to the master
> database where the new proc has been created. But it is not displayed in
> the
> Stored Procs of the master either.
> What has gone wrong? I should be able to create new stored procs in my
> database and not in the master database.
> Can someone help - thanks|||Thanks for your response. Unfortunately it makes no difference. I created th
e
new proc and then opened it, but the Connect to Database Engine dialog box i
s
displayed and I connect to the master db.
"Uri Dimant" wrote:

> Lisa
> What is happenening if you issue?
> USE mydb
> GO
> CREATE PROC mmmm
> AS
> .....
>
> "Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in messag
e
> news:430A9254-6539-4C84-8C57-DBC4E3C0AADA@.microsoft.com...
>
>|||Lisa
Ok, it is by default. You can change it by using
EXEC sp_defaultdb 'Lisa', 'AdventureWorks'
"Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in message
news:16DB04B0-8E9B-4C8C-88FD-F881A31AA781@.microsoft.com...[vbcol=seagreen]
> Thanks for your response. Unfortunately it makes no difference. I created
> the
> new proc and then opened it, but the Connect to Database Engine dialog box
> is
> displayed and I connect to the master db.
>
> "Uri Dimant" wrote:
>|||Uri
I don't want to seem ignorant but where do I use this. I'm using Access as
my front end and SQLExpress as the backend.
Also - I'm not able to modify any of the previous stored procs. If I make a
modification and save by overwriting the proc, the changes are not there whe
n
I open the proc again.
"Uri Dimant" wrote:

> Lisa
> Ok, it is by default. You can change it by using
> EXEC sp_defaultdb 'Lisa', 'AdventureWorks'
> "Lisa Tanenbaum" <LisaTanenbaum@.discussions.microsoft.com> wrote in messag
e
> news:16DB04B0-8E9B-4C8C-88FD-F881A31AA781@.microsoft.com...
>
>