Here is the objective.  I want to have 2 DNN sites using the same database.

Assumptions:
1. I have a functioning DNN installation in a directory called "home".  There is no "objectQualifier" here, so the database objects are created with no prefix.

Steps:
1. Create a new directory called "storetest".  Set permissions on directory, set to use ASP.net 2.0, etc.
2. Copy fresh DNN files into directory.
3. Rename release.config to web.config and plug in the connectionstring.  I know the connectionstring is valid because it's the same one I use for my functioning DNN site.
4. Set the objectQualifer to "store_".
5. Restart IIS
6. Run the www.whatever.com/storetest/ website, which redirects to /install/default.aspx?mode=Install

Results:
1. I get a message stating "cannot find store_GetPortalId()".
2. If I refresh, I get a message:
  Nothing To Install At This Time
  Current Assembly Version: 04.00.02
  Current Database Version: 04.00.02

So what gives?  I've verified that no database objects were created with the "store_" prefix, so I have no idea why the second time it says "nothing to install".  I've also verified that the "InstallationDate" key doesn't exist.

Of course I don't know why the first time it immediately tried to execute "store_GetPortalId()" function without first creating it. 

This is extremely frustrating, I'm trying to set up a demo for a client, but my ISP has given me only 1 database I can use.  Somebody must have already bumped heads with this issue already...

Anybody out there successfully installed two DNN installations into the same database?

As I see it, it seems like a vaporware promise.  Sure some underlying code is there to support it, but in practice it doesn't work, certainly not "as advertised" where you can just change the "objectQualifier" and let it install.

I'm curious to talk to somebody who's actually done it to find out what steps I am missing.

If you mean the /install/ directory of the second website I am trying to create, then no such file exists.

The closest filename is DotNetNuke.Install.Config.  I renamed that, with no success.

Now when I go to "/Install/Install.aspx" it tells me there is nothing to install at this time.

But when I try to go to the website directly (default.aspx) it tells me :

    The stored procedure 'dbo.storetest_GetPortalAliasByPortalID' doesn't exist.

No stored procedures have been created with the "storetest_" prefix.  So why won't the installer do it for me?  Is there another way to run the DDL and set up a DNN website other than the built-in Install.aspx method?