Default Instance

Our installation of SQL server 2000 has been installed as
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?
Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?
|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?
|||Will this restore the security, or will I have to restore
the Master DB as well?

>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
as[vbcol=seagreen]
I[vbcol=seagreen]
run[vbcol=seagreen]
I[vbcol=seagreen]
server?
>
>.
>
|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx.gbl...[vbcol=seagreen]
> Will this restore the security, or will I have to restore
> the Master DB as well?
> databases back by
> (PASS) and it's
> message
> as
> I
> run
> I
> server?

Default Instance

Our installation of SQL server 2000 has been installed as
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||Will this restore the security, or will I have to restore
the Master DB as well?

>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
> news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
as[vbcol=seagreen]
I[vbcol=seagreen]
run[vbcol=seagreen]
I[vbcol=seagreen]
server?[vbcol=seagreen]
>
>.
>|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx
.gbl...[vbcol=seagreen]
> Will this restore the security, or will I have to restore
> the Master DB as well?
>
> databases back by
> (PASS) and it's
> message
> as
> I
> run
> I
> server?sql

default database

Hi all,
I want to delete a particular database 'r3risk', But when I delete it, I
have problems when connecting via sqlmanager. It gives me an error about the
default database, which is set at 'r3risk', which I've deleted. I've had to
restore and reatach in order to connect via sql manager.
Where and how can I change what the default database is. SQL manager options
in the database properties is greyed out.
Thanks
RobertEasiest is to use sp_defaultdb.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Robert Bravery" <me@.u.com> wrote in message news:eKg6bNWPGHA.2696@.TK2MSFTNGP14.phx.gbl...[
color=darkred]
> Hi all,
> I want to delete a particular database 'r3risk', But when I delete it, I
> have problems when connecting via sqlmanager. It gives me an error about t
he
> default database, which is set at 'r3risk', which I've deleted. I've had t
o
> restore and reatach in order to connect via sql manager.
> Where and how can I change what the default database is. SQL manager optio
ns
> in the database properties is greyed out.
> Thanks
> Robert
>[/color]

debugging stored procedure

Hi everyone,
For some reason our stored procedure is returning an error when
executed. As part of resolving where the point of failure occurs, I
have defined an OUT variable to return what stage within the stored
procedure execution has reached before failure:
CREATE PROCEDURE sp_generate_invoices @.id char(14), @.retval int = 0 OUT
AS
BEGIN
<code>
SET @.retvalue = 1
<more code>
SET @.retvalue = 2
...
END
RETURN 1
GO
--
My question is, if the stored procedure fails half way through (for
whatever reason for example an overflow error), is the @.retval value
prior to the failure actually returned when the procedure fails? Or is
the default value returned whenever failure occurs?
If not, I am guessing the best method to track where the point of
failure occurs is to include statements like:
insert flowcontrol (datestamp, position)
value (getdate(), '1')
... throughout the code.
Any insight into this most appreciated!
thanks,
peterSimplest way would be to use @.@.ERROR to trap for error conditions and using
PRINT statements to debug your flow.
--
HTH,
SriSamp
Email: srisamp@.gmail.com
Blog: http://blogs.sqlxml.org/srinivassampath
URL: http://www32.brinkster.com/srisamp
<mag1kus@.yahoo.com> wrote in message
news:1141009017.876445.302420@.p10g2000cwp.googlegroups.com...
> Hi everyone,
> For some reason our stored procedure is returning an error when
> executed. As part of resolving where the point of failure occurs, I
> have defined an OUT variable to return what stage within the stored
> procedure execution has reached before failure:
> --
> CREATE PROCEDURE sp_generate_invoices @.id char(14), @.retval int = 0 OUT
> AS
> BEGIN
> <code>
> SET @.retvalue = 1
> <more code>
> SET @.retvalue = 2
> ...
> END
> RETURN 1
> GO
> --
> My question is, if the stored procedure fails half way through (for
> whatever reason for example an overflow error), is the @.retval value
> prior to the failure actually returned when the procedure fails? Or is
> the default value returned whenever failure occurs?
> If not, I am guessing the best method to track where the point of
> failure occurs is to include statements like:
> insert flowcontrol (datestamp, position)
> value (getdate(), '1')
> ... throughout the code.
> Any insight into this most appreciated!
> thanks,
> peter
>