471,571 Members | 1,015 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,571 software developers and data experts.

SQL server 2005 Express - Vista - Invalid object name '#spdbdesc'

I'm running Vista Business edition on 2005 Virtual PC.
Installed SQL Server 2005 Express latest download, with instance of
MSSQLSERVER and service accounts running under "NT AUTHORITY\SYSTEM".
Mixed mode authentication specified and sa password specified.
Used server manager to create user login with sysadmin role.
Login using windows authentication.

Run my application and database is created and populated with default
records.

However, my application executes the stored procedure "sp_helpdb"
which fails with "Invalid object name '#spdbdesc'" error.

If I run a query in server manager to execute same procedure logged
in
as the same person it runs ok and returns a table of information.

All this was working ok on XP with MSDE2000A previously.

I'm programming in .NET C# CLR2.0, any body know what's going wrong?

Apr 2 '07 #1
3 7270
This question was also posted and answered in
microsoft.public.sqlserver.programming. If you need to post the same
question to multiple groups, post the message once to all groups in order to
avoid duplication of effort.

However, my application executes the stored procedure "sp_helpdb"
which fails with "Invalid object name '#spdbdesc'" error.
Perhaps the application is retrieving result set meta-data with SET FMTONLY
ON. This will result in an error since the #spdbdesc temp table does not
exist when the proc is executed with SET FMTONLY ON.
I'm programming in .NET C# CLR2.0, any body know what's going wrong?
It's difficult to say without seeing your code. The snippet below works for
me with SQL Server Developer Edition under Vista. I would expect it to work
under SQL Express too.
DataTable dt = new DataTable();
SqlConnection connection =
new SqlConnection("Data Source=(local);Integrated Security=SSPI");
SqlCommand command =
new SqlCommand("sp_helpdb", connection);
command.CommandType = CommandType.StoredProcedure;
SqlDataAdapter da = new SqlDataAdapter(command);
connection.Open();
da.Fill(dt);
connection.Close();

--
Hope this helps.

Dan Guzman
SQL Server MVP

<ia************@hotmail.co.ukwrote in message
news:11**********************@b75g2000hsg.googlegr oups.com...
I'm running Vista Business edition on 2005 Virtual PC.
Installed SQL Server 2005 Express latest download, with instance of
MSSQLSERVER and service accounts running under "NT AUTHORITY\SYSTEM".
Mixed mode authentication specified and sa password specified.
Used server manager to create user login with sysadmin role.
Login using windows authentication.

Run my application and database is created and populated with default
records.

However, my application executes the stored procedure "sp_helpdb"
which fails with "Invalid object name '#spdbdesc'" error.

If I run a query in server manager to execute same procedure logged
in
as the same person it runs ok and returns a table of information.

All this was working ok on XP with MSDE2000A previously.

I'm programming in .NET C# CLR2.0, any body know what's going wrong?
Apr 2 '07 #2
On 2 Apr, 13:39, "Dan Guzman" <guzma...@nospam-online.sbcglobal.net>
wrote:
This question was also posted and answered in
microsoft.public.sqlserver.programming. If you need to post the same
question to multiple groups, post the message once to all groups in order to
avoid duplication of effort.
Snip
>
Dan Guzman
SQL Server MVP
Snip

Sorry for that, it's the first time I've posted in many years...

If I don't specify SET FMTONLY ON/OFF in my code is there a default
state that I can rely on?
Is it the same for all SQL implementations?
If not, should I set it when opening the connection?

Many thanks

Ian
Apr 2 '07 #3
(ia************@hotmail.co.uk) writes:
If I don't specify SET FMTONLY ON/OFF in my code is there a default
state that I can rely on?
SET FMTONLY ON is usually submitted behind the scenes. ADO Classic
is notorious for doing this without being asked. ADO .Net is far more
well-behaved. But if you use CommandBehaviour.MetaDataOnly, there is a
SET FMTONLY sent to SQL Server.
Is it the same for all SQL implementations?
It's the client API that gets the idea to issue SET FMTONLY ON, so the
version of SQL Server should not matter.

It could certainly help if you could post your code.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
Apr 2 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Arpan | last post: by
2 posts views Thread by kress1963nov22 | last post: by
3 posts views Thread by sgottenyc | last post: by
reply views Thread by XIAOLAOHU | last post: by
reply views Thread by Vinnie | last post: by
reply views Thread by lumer26 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.