"Local" Server

All:
I was using a 120 day eval of SQL Server, and then purchased the developers
edition. During the install....and don't ask me exactly how I did it, I
ended up naming my "new" server TVB\TVB - the old one was just TVB, and I
managed to remove the TVB and now have no "local" server, so to speak. I
can't find the setting to rectify this, although the database works
OK...but when using connection strings, I can't use localhost in the code,
I have to use the actual name, fortunately I can still use it in the URL.
This is probably easy to rectify if one knows where to look or what to do,
and I fear this may cause a problem bigger than the minor annoyance it is
now down the line. (Plus I only have a few apps set up , many more to come)
Advice greatly appreciated, thanks in advance.
Tom BThe only way to rectify this is to uninstall the named instance and
reinstall as a default instance. You cannot rename a SQL Server named
instance. If you have databases you want to keep then you can back them up
or detach them before uninstalling and then restore or attach them to your
default instance (that will have the same name as the server)
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tom Bernsen" <t.bernsen@.worldnet.att.net> wrote in message
news:%23VGj0hN9DHA.2064@.TK2MSFTNGP11.phx.gbl...
> All:
> I was using a 120 day eval of SQL Server, and then purchased the
developers
> edition. During the install....and don't ask me exactly how I did it, I
> ended up naming my "new" server TVB\TVB - the old one was just TVB, and I
> managed to remove the TVB and now have no "local" server, so to speak. I
> can't find the setting to rectify this, although the database works
> OK...but when using connection strings, I can't use localhost in the
code,
> I have to use the actual name, fortunately I can still use it in the URL.
> This is probably easy to rectify if one knows where to look or what to do,
> and I fear this may cause a problem bigger than the minor annoyance it is
> now down the line. (Plus I only have a few apps set up , many more to
come)
> Advice greatly appreciated, thanks in advance.
> Tom B
>

"Could not find stored procedure 'sp_sdidebug'" SQL 2005 VERY URGENT

Hi all
i have installed SQL 2005
and when i try to run my application it gives me this error .
Could not find stored procedure 'sp_sdidebug' what can i do to solve this
...
thks
JSBIns Pires wrote:
> Hi all
> i have installed SQL 2005
> and when i try to run my application it gives me this error .
> Could not find stored procedure 'sp_sdidebug' what can i do to solve
> this ...
> thks
> JSB
Pulled from somewhere out there:
"Also, a little tip about upgrading apps from .NET 1.1 to 2.0 for use with
SQL Server 2005: If in debug mode, you get an error stating that sp_sdidebug
was not found if you have checked debug SQL Server code in your project
properties. This goes away when you uncheck. "
David Gugick
Quest Software|||thks David,
thks for the tip.
and if i need to run with the debug on ' how can i solve it ?
thks
IP
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:O0vCQla4FHA.2196@.tk2msftngp13.phx.gbl...
> Ins Pires wrote:
> Pulled from somewhere out there:
> "Also, a little tip about upgrading apps from .NET 1.1 to 2.0 for use with
> SQL Server 2005: If in debug mode, you get an error stating that
> sp_sdidebug was not found if you have checked debug SQL Server code in
> your project properties. This goes away when you uncheck. "
>
> --
> David Gugick
> Quest Software
>|||Ins Pires wrote:
> thks David,
> thks for the tip.
> and if i need to run with the debug on ' how can i solve it ?
> thks
> IP
>
You might need VS.Net 2005. Not sure.
David Gugick
Quest Software

"Could not find stored procedure 'sp_sdidebug'" SQL 2005 VERY URGENT

Hi all
i have installed SQL 2005
and when i try to run my application it gives me this error .
Could not find stored procedure 'sp_sdidebug' what can i do to solve this
...
thks
JSB
Ins Pires wrote:
> Hi all
> i have installed SQL 2005
> and when i try to run my application it gives me this error .
> Could not find stored procedure 'sp_sdidebug' what can i do to solve
> this ...
> thks
> JSB
Pulled from somewhere out there:
"Also, a little tip about upgrading apps from .NET 1.1 to 2.0 for use with
SQL Server 2005: If in debug mode, you get an error stating that sp_sdidebug
was not found if you have checked debug SQL Server code in your project
properties. This goes away when you uncheck. "
David Gugick
Quest Software
|||thks David,
thks for the tip.
and if i need to run with the debug on ? how can i solve it ?
thks
IP
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:O0vCQla4FHA.2196@.tk2msftngp13.phx.gbl...
> Ins Pires wrote:
> Pulled from somewhere out there:
> "Also, a little tip about upgrading apps from .NET 1.1 to 2.0 for use with
> SQL Server 2005: If in debug mode, you get an error stating that
> sp_sdidebug was not found if you have checked debug SQL Server code in
> your project properties. This goes away when you uncheck. "
>
> --
> David Gugick
> Quest Software
>
|||Ins Pires wrote:
> thks David,
> thks for the tip.
> and if i need to run with the debug on ? how can i solve it ?
> thks
> IP
>
You might need VS.Net 2005. Not sure.
David Gugick
Quest Software