We have been using this method of forcing the catalog name in the generated sql (cut and pasted from the docs):

<configuration>
    <appSettings>
        <add key="Main.ConnectionString" value="data source=..."/>
        <add key="CatalogNameUsageSetting" value="1"/>
        <add key="CatalogNameToUse" value="MyProductionCatalog" />
        ...
    </appSettings>
</configuration>

So code similar to what is above is used in the staging/prod environment, and it is commented out in test. The Main.ConnectionString value is the same for all three environments.

The problem is, we have the "initial catalog" setting as part of the Main.Connectionstring. We discovered that when the initial catalogue (which is the test catalog that we generate from) was taken offline, all the sites went down.

Are we doing something wrong? Should we be changing the initial catalog in the web.config as well as adding the override code, or is there a workaround for this? I realize there are newer, better ways to manage this now.

Thanks,

Phil

I believe that you should change the catalog in both areas. If my understanding is correct the CatalogNameToUse is more for when generating the sql, CatalogNameToUse.Table.Field. The connectionstring is used to open the connection to the database.

To elaborate a bit more: the catalog mentioned in the connection string is the catalog you will connect to after the user/password has been accepted by sqlserver. So if that catalog isn't there, sqlserver can't connect you to a catalog and it fails.

So specify one of the catalogs you will work with for sure in the connection string, or don't take the initial catalog offline.

Thanks, gents. If no initial catalogue is specified, it goes to the default catalog for the user (assuming SQL Server)?

I'm guessing this has more to do with SQL Server connection strings than LLBL?

Correct.