Diagram of Master DB

Is there a way to get the diagram of the MASTER Db in MS-SQL? When i
right click on Enterprise Manager that option is not available but it
is available in any other database (Model Db acts the same).

Thanks,

GentI don't know why that option is disabled for system DBs, but you can
get a full diagram of all the system tables here:

http://www.microsoft.com/sql/techin...0/systables.asp

Simon|||I'm new here. Sorry if this has already been covered. Is there a way to
generate full diagrams for the tables you create? Thanks.

- Bob

"Simon Hayes" <sql@.hayes.ch> wrote in message
news:1114159237.222700.21110@.g14g2000cwa.googlegro ups.com...
> I don't know why that option is disabled for system DBs, but you can
> get a full diagram of all the system tables here:
> http://www.microsoft.com/sql/techin...0/systables.asp
> Simon|||farrell77 (farrell77@.spamfree.yahoo.com) writes:
> I'm new here. Sorry if this has already been covered. Is there a way to
> generate full diagrams for the tables you create? Thanks.

You can generate diagrams of your database from Enterprise Manager.
Right-click your database and select New->Database diagram.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Device holding MASTER, MODEL, MSDB, and TempDB FULL

I have other drives that are quite large that I could move any one of these
to. Not sure how to do the move...this is a production server and down
time needs to be almost non-existent.
TempDB is taking up 1 gig, if there was a way to move it without bringing
down the server, that would be great (like adding a file to new drive, then
shrinking with EMPTY_FILE on old drive.....can this be done during
production or would it cause slowness or locking, etc.?)What version of SQL Server are you using ...?
Have you tried Shrinking it. DBCC SHRINKFILE
HTH
Ryan Waight, MCDBA, MCSE
"John Hamilton" <jhamil@.nowhere.com> wrote in message
news:ODt9rtJnDHA.2528@.TK2MSFTNGP12.phx.gbl...
> I have other drives that are quite large that I could move any one of
these
> to. Not sure how to do the move...this is a production server and down
> time needs to be almost non-existent.
> TempDB is taking up 1 gig, if there was a way to move it without bringing
> down the server, that would be great (like adding a file to new drive,
then
> shrinking with EMPTY_FILE on old drive.....can this be done during
> production or would it cause slowness or locking, etc.?)
>|||I'm using 2000, and I tried DBCC SHRINKFILE, it didn't change the size.
"Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:eWnaIzJnDHA.2012@.TK2MSFTNGP12.phx.gbl...
> What version of SQL Server are you using ...?
> Have you tried Shrinking it. DBCC SHRINKFILE
>
> --
> HTH
> Ryan Waight, MCDBA, MCSE
> "John Hamilton" <jhamil@.nowhere.com> wrote in message
> news:ODt9rtJnDHA.2528@.TK2MSFTNGP12.phx.gbl...
> > I have other drives that are quite large that I could move any one of
> these
> > to. Not sure how to do the move...this is a production server and down
> > time needs to be almost non-existent.
> >
> > TempDB is taking up 1 gig, if there was a way to move it without
bringing
> > down the server, that would be great (like adding a file to new drive,
> then
> > shrinking with EMPTY_FILE on old drive.....can this be done during
> > production or would it cause slowness or locking, etc.?)
> >
> >
>|||Tried SHRINKFILE again and it worked this time....'?
"Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:eWnaIzJnDHA.2012@.TK2MSFTNGP12.phx.gbl...
> What version of SQL Server are you using ...?
> Have you tried Shrinking it. DBCC SHRINKFILE
>
> --
> HTH
> Ryan Waight, MCDBA, MCSE
> "John Hamilton" <jhamil@.nowhere.com> wrote in message
> news:ODt9rtJnDHA.2528@.TK2MSFTNGP12.phx.gbl...
> > I have other drives that are quite large that I could move any one of
> these
> > to. Not sure how to do the move...this is a production server and down
> > time needs to be almost non-existent.
> >
> > TempDB is taking up 1 gig, if there was a way to move it without
bringing
> > down the server, that would be great (like adding a file to new drive,
> then
> > shrinking with EMPTY_FILE on old drive.....can this be done during
> > production or would it cause slowness or locking, etc.?)
> >
> >
>|||Have a look at this :- http://www.aspfaq.com/show.asp?id=2446
good for future reference..
--
HTH
Ryan Waight, MCDBA, MCSE
"John Hamilton" <jhamil@.nowhere.com> wrote in message
news:%234Iku4JnDHA.2080@.TK2MSFTNGP10.phx.gbl...
> Tried SHRINKFILE again and it worked this time....'?
>
> "Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
> news:eWnaIzJnDHA.2012@.TK2MSFTNGP12.phx.gbl...
> > What version of SQL Server are you using ...?
> >
> > Have you tried Shrinking it. DBCC SHRINKFILE
> >
> >
> >
> > --
> > HTH
> > Ryan Waight, MCDBA, MCSE
> >
> > "John Hamilton" <jhamil@.nowhere.com> wrote in message
> > news:ODt9rtJnDHA.2528@.TK2MSFTNGP12.phx.gbl...
> > > I have other drives that are quite large that I could move any one of
> > these
> > > to. Not sure how to do the move...this is a production server and
down
> > > time needs to be almost non-existent.
> > >
> > > TempDB is taking up 1 gig, if there was a way to move it without
> bringing
> > > down the server, that would be great (like adding a file to new drive,
> > then
> > > shrinking with EMPTY_FILE on old drive.....can this be done during
> > > production or would it cause slowness or locking, etc.?)
> > >
> > >
> >
> >
>|||This would indicate an open transaction was preventing the shrink. DBCC
OPENTRAN shows any open transcations
--
HTH
Ryan Waight, MCDBA, MCSE
"John Hamilton" <jhamil@.nowhere.com> wrote in message
news:%234Iku4JnDHA.2080@.TK2MSFTNGP10.phx.gbl...
> Tried SHRINKFILE again and it worked this time....'?
>
> "Ryan Waight" <Ryan_Waight@.nospam.hotmail.com> wrote in message
> news:eWnaIzJnDHA.2012@.TK2MSFTNGP12.phx.gbl...
> > What version of SQL Server are you using ...?
> >
> > Have you tried Shrinking it. DBCC SHRINKFILE
> >
> >
> >
> > --
> > HTH
> > Ryan Waight, MCDBA, MCSE
> >
> > "John Hamilton" <jhamil@.nowhere.com> wrote in message
> > news:ODt9rtJnDHA.2528@.TK2MSFTNGP12.phx.gbl...
> > > I have other drives that are quite large that I could move any one of
> > these
> > > to. Not sure how to do the move...this is a production server and
down
> > > time needs to be almost non-existent.
> > >
> > > TempDB is taking up 1 gig, if there was a way to move it without
> bringing
> > > down the server, that would be great (like adding a file to new drive,
> > then
> > > shrinking with EMPTY_FILE on old drive.....can this be done during
> > > production or would it cause slowness or locking, etc.?)
> > >
> > >
> >
> >
>

Developer terminates MSSQLSERVER service

Hi.
One of the developers tried to compile a stored procedure
against the master database by mistake. The result was
that the .
In the event log the following entry appears:
The system has called a custom component and that
component has failed and generated an exception.
This indicates a problem with the custom component.
Notify the developer of this component that a failure has
occurred and provide them with the information below.
Component Prog ID: SC. Pool 61 1
Method Name: IDispenseDriver::CreateResource
Process Name: sqlserver.exe
The serious nature of this error has caused the process
to terminate.
Exception: C0000005
Address: 0x17CEA9E1
Call Stack: 0x17CEA9E2
The MSSQLSERVER service terminated unexpectedly.
Just prior to that an entry appears with the developers
user id:
Error: 0, Severity:19 State:0
SqlDumpExceptionHandler: Process 167 generated fatal
exception = C0000005
EXCEPTION_ACCESS_VIOLATION SQL Server is terminating this
process.
How can I prevent this from ever happening again?
How can I lock down my server properly enough to prevent
this from ever happening again?
Thanks,
MTAV's are generally bugs in SQL Server, and you cannot make sure that SQL Server is bug free. When
you hit an AV, search KB, make sure the db is OK (CHECKDB) and if needed open a case with MS.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"MT" <anonymous@.discussions.microsoft.com> wrote in message
news:068d01c39eb8$9e372110$a601280a@.phx.gbl...
> Hi.
> One of the developers tried to compile a stored procedure
> against the master database by mistake. The result was
> that the .
> In the event log the following entry appears:
> The system has called a custom component and that
> component has failed and generated an exception.
> This indicates a problem with the custom component.
> Notify the developer of this component that a failure has
> occurred and provide them with the information below.
> Component Prog ID: SC. Pool 61 1
> Method Name: IDispenseDriver::CreateResource
> Process Name: sqlserver.exe
> The serious nature of this error has caused the process
> to terminate.
> Exception: C0000005
> Address: 0x17CEA9E1
> Call Stack: 0x17CEA9E2
> The MSSQLSERVER service terminated unexpectedly.
> Just prior to that an entry appears with the developers
> user id:
> Error: 0, Severity:19 State:0
> SqlDumpExceptionHandler: Process 167 generated fatal
> exception = C0000005
> EXCEPTION_ACCESS_VIOLATION SQL Server is terminating this
> process.
> How can I prevent this from ever happening again?
> How can I lock down my server properly enough to prevent
> this from ever happening again?
> Thanks,
> MT
>|||Thanks Tibor,
Good news, I ran the CHECKDB and found 0 allocation
errors and 0 consistency errors in database 'master'.
What does AV stand for? Under what criteria would I
search the KB to determine how to prevent this situation
from happening again
Thanks,
MT
>--Original Message--
>AV's are generally bugs in SQL Server, and you cannot
make sure that SQL Server is bug free. When
>you hit an AV, search KB, make sure the db is OK
(CHECKDB) and if needed open a case with MS.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"MT" <anonymous@.discussions.microsoft.com> wrote in
message
>news:068d01c39eb8$9e372110$a601280a@.phx.gbl...
>> Hi.
>> One of the developers tried to compile a stored
procedure
>> against the master database by mistake. The result was
>> that the .
>> In the event log the following entry appears:
>> The system has called a custom component and that
>> component has failed and generated an exception.
>> This indicates a problem with the custom component.
>> Notify the developer of this component that a failure
has
>> occurred and provide them with the information below.
>> Component Prog ID: SC. Pool 61 1
>> Method Name: IDispenseDriver::CreateResource
>> Process Name: sqlserver.exe
>> The serious nature of this error has caused the process
>> to terminate.
>> Exception: C0000005
>> Address: 0x17CEA9E1
>> Call Stack: 0x17CEA9E2
>> The MSSQLSERVER service terminated unexpectedly.
>> Just prior to that an entry appears with the developers
>> user id:
>> Error: 0, Severity:19 State:0
>> SqlDumpExceptionHandler: Process 167 generated fatal
>> exception = C0000005
>> EXCEPTION_ACCESS_VIOLATION SQL Server is terminating
this
>> process.
>> How can I prevent this from ever happening again?
>> How can I lock down my server properly enough to
prevent
>> this from ever happening again?
>> Thanks,
>> MT
>>
>
>.
>|||AV is short for Access Violation (see the error messages that SQL Server returned). You would have
to try to find a relevant KB article by going in a good search string, error number etc. However,
there might not be a KB article for your problem (the bug in SQL Server might not be knows, yet),
hence the need to possibly open a case with MS support. If you find a KB article, it hopefully has
some workaround, point to some service pack that fixes this or possibly a hotfix that fixes this.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"MT" <anonymous@.discussions.microsoft.com> wrote in message
news:06b301c39ebc$a80b02c0$a601280a@.phx.gbl...
> Thanks Tibor,
> Good news, I ran the CHECKDB and found 0 allocation
> errors and 0 consistency errors in database 'master'.
> What does AV stand for? Under what criteria would I
> search the KB to determine how to prevent this situation
> from happening again
> Thanks,
> MT
> >--Original Message--
> >AV's are generally bugs in SQL Server, and you cannot
> make sure that SQL Server is bug free. When
> >you hit an AV, search KB, make sure the db is OK
> (CHECKDB) and if needed open a case with MS.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"MT" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:068d01c39eb8$9e372110$a601280a@.phx.gbl...
> >> Hi.
> >>
> >> One of the developers tried to compile a stored
> procedure
> >> against the master database by mistake. The result was
> >> that the .
> >>
> >> In the event log the following entry appears:
> >>
> >> The system has called a custom component and that
> >> component has failed and generated an exception.
> >> This indicates a problem with the custom component.
> >> Notify the developer of this component that a failure
> has
> >> occurred and provide them with the information below.
> >>
> >> Component Prog ID: SC. Pool 61 1
> >> Method Name: IDispenseDriver::CreateResource
> >> Process Name: sqlserver.exe
> >>
> >> The serious nature of this error has caused the process
> >> to terminate.
> >>
> >> Exception: C0000005
> >> Address: 0x17CEA9E1
> >> Call Stack: 0x17CEA9E2
> >>
> >> The MSSQLSERVER service terminated unexpectedly.
> >>
> >> Just prior to that an entry appears with the developers
> >> user id:
> >>
> >> Error: 0, Severity:19 State:0
> >> SqlDumpExceptionHandler: Process 167 generated fatal
> >> exception = C0000005
> >>
> >> EXCEPTION_ACCESS_VIOLATION SQL Server is terminating
> this
> >> process.
> >>
> >> How can I prevent this from ever happening again?
> >> How can I lock down my server properly enough to
> prevent
> >> this from ever happening again?
> >>
> >> Thanks,
> >> MT
> >>
> >>
> >
> >
> >.
> >