"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
JSBInês 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...
> Inês 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
>|||Inês 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
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

Urgent Please Help - Conserving Page Real Estate

When the page header properties are set as 'PrintOnFirstPage' = False, so
that it doesn't show on the first page, it still seems to take up space on
the first page.
Is there a way to compress this space?
The pseudo report header that I created in the body (to show up only on page
1) is showing up about an inch lower than it really should when the report
renders. I am thinking that this is probably because the page header space
is still being consumed, even though it isn't literally being printed there.
Am I right? Is there a way to conserve that page real estate?
Thanks,
LisaThis is a bug. I don't know of any way to collapse out that space until we
get the bug fixed.
--
My employer's lawyers require me to say:
"This posting is provided 'AS IS' with no warranties, and confers no
rights."
"Lisa" <Lisa.Lambert@._nospam_etalk.com> wrote in message
news:O4ZqFEFZEHA.4092@.TK2MSFTNGP11.phx.gbl...
> When the page header properties are set as 'PrintOnFirstPage' = False, so
> that it doesn't show on the first page, it still seems to take up space on
> the first page.
> Is there a way to compress this space?
> The pseudo report header that I created in the body (to show up only on
page
> 1) is showing up about an inch lower than it really should when the report
> renders. I am thinking that this is probably because the page header
space
> is still being consumed, even though it isn't literally being printed
there.
> Am I right? Is there a way to conserve that page real estate?
> Thanks,
> Lisa
>
>|||Thank you.
"Chris Hays [MSFT]" <chays@.online.microsoft.com> wrote in message
news:u9OQBqFZEHA.3476@.tk2msftngp13.phx.gbl...
> This is a bug. I don't know of any way to collapse out that space until
we
> get the bug fixed.
> --
> My employer's lawyers require me to say:
> "This posting is provided 'AS IS' with no warranties, and confers no
> rights."
> "Lisa" <Lisa.Lambert@._nospam_etalk.com> wrote in message
> news:O4ZqFEFZEHA.4092@.TK2MSFTNGP11.phx.gbl...
> > When the page header properties are set as 'PrintOnFirstPage' = False,
so
> > that it doesn't show on the first page, it still seems to take up space
on
> > the first page.
> > Is there a way to compress this space?
> >
> > The pseudo report header that I created in the body (to show up only on
> page
> > 1) is showing up about an inch lower than it really should when the
report
> > renders. I am thinking that this is probably because the page header
> space
> > is still being consumed, even though it isn't literally being printed
> there.
> > Am I right? Is there a way to conserve that page real estate?
> >
> > Thanks,
> >
> > Lisa
> >
> >
> >
>