Re: ASP.net insists on using dbo. to call aspnet_* stored procedures

re:
!> dbo.myobject should be the same as mysql_login.myobject, right?

No. mysql_login is one account and the dbo is another account,
unless you use the changedbowner stored procedure to change
database ownership from dbo to mysql_login.

Try this in the query analyzer :

EXEC sp_changedbowner 'mysql_login'

That will, effectively, make the mysql_login the dbo and should end your problems.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Pedro Vera" <pedro.vera@xxxxxxxxx> wrote in message
news:1175264766.470857.90940@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks so much for the almost instant reply!

Here is a bit more info:

Local version:

XP Pro SP2, SQL Server 2000 developer in same machine. The connection
string is setup to use the sa login and password. Everything works
peachy.

Remote version:

2003 server, no idea SP. SQL Server 2000 in a different machine. The
connection string is setup to use the sql login assigned to the
hosting account, call it "mysql_login". At least the connection string
works, because I am not getting a bad connection string error.

Here is what I don't understand. I would assume that if I am user
mysql_login, and I create an object, then if I use that login then
dbo.myobject should be the same as mysql_login.myobject, right? In my
usual projects at work I have not run into this issue, so I should
start checking if maybe that host has screwed up the sql server
permissions.

Thanks,

Pedro Vera
http://veraperez.com


On Mar 30, 10:08 am, "Cowboy \(Gregory A. Beamer\)"
<NoSpamMgbwo...@xxxxxxxxxxxxxxxxxx> wrote:
dbo is the schema used in SQL Server and, even if removed from queries, is
technically still there. Unless, of course, you have created a new schema
and own the objects in question. It sounds more like a permissions error or
connectivity problem than a dbo problem.

Is SQL Server on the same box as your application? If not, turn on the SQL
Browser service. If this is a default install, you may also have to turn on
a protocol other than Managed Local (or whatever it is called). TCP/IP is a
good one to turn on in most cases; you can also try named pipes.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBAhttp://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
*********************************************"Pedro Vera" <pedro.v...@xxxxxxxxx> wrote in message

news:1175261450.698261.35410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I am helping somebody setup one of the asp.net starter kits. I
converted it from sql express to sql server with no real issues, and I
got it running local perfectly.

On my first attempt to run it remotely I noticed that a lot of the
queries had dbo. hardcoded and that SQL server on the remote server
was not allowing my sql account access to these. I removed all
mentions of dbo. and again it still runs local. I have posted it to
the remote server once again, but I still get errors like this:

Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'

Now, the common sense answer here is that the remote database was not
primed properly with:




C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe

But this is not true. The remote db was primed properly and I can run
aspnet_* stored procedures from enterprise manager logged in using the
same account used in the connection string.

Any idea how I can go around this? My worst case scenario is to grab a
clean copy of the starter kit and instead of removing dbo., changing
it from dbo. to mysqlusername. and see if that helps.

Thanks,

Pedro Vera
http://veraperez.com




.

Relevant Pages

  • Re: Connect pocket pc (2003) to sql sever in trusted/integrated/ss
    ... it was SQL Server that was running in local system account. ... Here's connection string sample, note "Integrated Security=SSPI". ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: DBO Best Practices
    ... lines of always owner qualifying objects... ... someone who are just "a" dbo. ... > doesn't explicitly reference the object's owner (because SQL Server will ... The startup account defines the ...
    (microsoft.public.sqlserver.security)
  • Re: ASP.net insists on using dbo. to call aspnet_* stored procedures
    ... The easiest way to get around this is to use the sp_changeobjectowner stored procedure which will ... SQL Server 2000 developer in same machine. ... connection string is setup to use the sql login assigned to the ... connectivity problem than a dbo problem. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: DBO Best Practices
    ... If you let DBO own databases or objects then regular ... Please note that the DBO user is identified by the SQL Server process ... the SQL Server startup account (for the ... SQL Server process) controls SQL Server's ability to work with NT's objects ...
    (microsoft.public.sqlserver.security)
  • Unable to use Kerberos Delegation from IE6 --> IIS 5.0 (asp.net)--> SQL 2000
    ... When attempting to make a connection using ADO.NET connection string: ... W2K member Server SP3 ... SQL Server configured for TCP/IP Protocol Only ... COMPUTER\SQL_MYSQL is marked as Account is trusted for delegation NOT REQUIRED??? ...
    (microsoft.public.sqlserver.security)