[QUOTE]


frankt wrote

The object qualifier is something that you can set in your web.config file that will prefice all of the database tables, stored procedures, views, foriegn key constraints, etc... with this prefix. It is set in your web.config file in this section. In the example below, the object qualifier is set to dnn_ so the portalalias table would be created as dnn_portalalias in the install scripts. Also note the databaseowner field to. This should be set to the account in sql server that owns the schema (in most cases this is just dbo, but if your sql server connection string uses a different account to login, you should make this that account.) Hope this helps

Thanks, Frank, for the description. It really helps towards filling in some gaps of my familiarity with databases. Before I forget, I think the post above might have chopped off some of the lines of code you intended to show. It always does that to me, anyway.

Now that really helps me to put together a few things. To point: I had noticed that in this database when I need to update a Portal Alias, I could not use:
update dnn_portalalias set httpalias= blah blah

This surprised me because I had used dnn_portalalias before with other DNN ver 4.x databases.

Indeed when I looked through the tables (I hope I am using the correct term, anyway) I could see that the table name was just dbo.PortalAlias . And not dbo.dnn_PortalAlias. So I lopped off the prefix and found that I was able to update/alter a value in a query command.

So your explanation closes out my understanding of that syntax.

However ...
it opens up a new question.

(1) Since the database I am working with here (remember, it's from DNN v.2 era) does not have tables with that prefix name, then does that mean that in the past at some point DotNetNuke switched from using just dbo.PortalAlias to dbo.dnn_PortalAlias ?

(2) If the answer is yes above, then I am quite certain I will need to use the _Update download when I next try this process, and not use the _Install download.

(3) Don't forget that the portal is seemingly being called up operationally, because when I start up the application via the web server, it thinks a bit and then does indeed call up a DNN-style URL. But that URL leads to just a blank page for now.


Thank you.