Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...objectQualifier not naming aspnet tables???objectQualifier not naming aspnet tables???
Previous
 
Next
New Post
3/2/2007 10:24 PM
 

i am installing dnn 4.4.1 on shared hosting, they use sql 2000.

i have changed settings within web.config


objectQualifier from dbo to dbo********

install gos fine no errors

the problem i have is after i have set up hosting disables my access to the 7x aspnet tables as the database owner is dbo and not dbo********

if i do a sql backup/restore it changes to database owner of the 7x aspnet tables to dbo******** but then dnn4.4.1 does not run as is looking for dbo.aspnet rather than the new dbo********.aspnet since restore.

is there a work around for this

either by script to update dnn to new names of database owner of aspnet tables, or to force dnn instal to name aspnet with dbo******** on initial install

 
New Post
3/3/2007 4:29 PM
 

objectQualifier does not affect the owner. It is just a string that gets prepended to the names of objects.

objectQualifier="??" databaseOwner="dbo"

databaseOwner would install as a particular user, which should have the dbo role for the database, unless you are using a different user (as specified in the upgradeConnectionString) for installing as this is the user that needs to be able to create tables, etc., whereas the other needs update, insert and delete on objects or at least execute on all stored procedures.

I would recommend that you consider a different host as this kind of micro-control of your database is to inhibiting.

Shared hosting shouldn't mean sharing a database with others. Share the SQL Server, yes, but your database should be yours alone. You should be able to drop it, create it, connect to it, create and drop tables, etc, as you wish.


pmgerholdt
 
New Post
3/3/2007 5:40 PM
 
pmichael wrote

objectQualifier="??" databaseOwner="dbo"

sorry my wording was wrong

here is an idea of the details changed within web.config
<add
      name="SiteSqlServer"
      connectionString="Server=mssql**.server.co.uk;Database=db12345678;uid=dbo12345678;pwd=********;"
      providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<add key="SiteSqlServer" value="Server=mssql**.server.co.uk;Database=db12345678;uid=dbo12345678;pwd=********;"/>
<add
          name="SqlDataProvider"
          type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider"
          connectionStringName="SiteSqlServer"
          upgradeConnectionString=""
          providerPath="~\Providers\DataProviders\SqlDataProvider\"
          objectQualifier=""
          databaseOwner="dbo12345678"/>

so database db12345678 uid dbo12345678

database is blank prior to install of dnn. once installed the aspnet tables datadase owner is dbo where as all other tables is dbo12345678.

hosting are saying that i am accessing database as unauthorised user and have banned access to all tables with dbo as database owner.

i just could not understand that if i was naming the database owner as dbo12345678 why aspnet tables owner was dbo

would change hosting is never had so many pop3 mail hosted with them

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...objectQualifier not naming aspnet tables???objectQualifier not naming aspnet tables???


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out