Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL dbo question

Status
Not open for further replies.

fireemt1

Technical User
Jul 14, 2003
16
US
Im having a problem with SQL 2000 and asp.net. This question is actually me trying to understand SQL better to trace the problem. Here is the link to the entire problem.


Background:
I am trying to access a external SQL 2000 server using ASP.NET using Membership services. The "call" calls for access to "dbo.aspnet_SchemaVersion" stored procedure. It reports that it is unable to find it. I know the connection to the database is good.

What I need to know:
My connection string involves the user name being 'uid="dboxxxxxxxxx"' The x's are numbers. The database shows owner being the "dboxxxxxxxx". When it calls "dbo.aspnet_SchemaVersion" stored procedure, does it compare the owner of the database to the uid in the connection string or should it actually try and call "dboxxxxxxxxx.aspnet_SchemaVersion". Any help would be greatly appreciated.

Can't seem to find a wealth of information on the web using Membership services and SQL 2000.
 
First thing to check is if your connection string is setting the initial catalog to the proper database. If this is the case, then start up profiler on your sql server and run the script. This will tell you what's happening. With the profiler, you can trace the entire event from start to finish. Also, keep in mind that sql server is usually case sensitive...so if the case is off, that could be a problem.
 
Thanks for the reply.

Yes the initial catalog is correct. To check, I created a test table in the db and accessed it from asp.net using SqlDataReader. Read back the information perfectly.

Downside is that I only have access to a web based sql admin page and no way to connect externally due to security reasons.
 
If the owner of the object is dboxxxxxx then you will need to call the object as dboxxxxxx.aspnet_SchemaVersion.

This is very standard for hosting companies.

When you create procedures tables, etc if you specify the object owner as dbo then you can call the object as dbo.aspnet_schemaVersion. If when you create the object you do not include the object owner you will need to use the dboxxxxxx when calling the object.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Thanks for all the help. It's 100% clear now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top