Activity overview
Latest activity by IbexMark
Please note that clearing the default database will always cause an error. To fix the issue described above, you must first set your target database manually to point to the localDB, Set as Default, and then change your target DB manually back to Azure. / comments
Please note that clearing the default database will always cause an error. To fix the issue described above, you must first set your target database manually to point to the localDB, Set as Defau...
No. I recently posted another question where I wanted the connection string for new users of the project to point to the correct database. If it did not, it would create a bit of a mess as they would point to the shadow database by default. See " Where does SQL Change Automation store the connection string to the development database". I have followed the recommendations of that post and changed the default database to point to the Azure development database. That solves the problem of a new developer pulling the project for the first time; he sees the Azure development database. Now, unfortunately, I cannot verify the project as the shadow database cannot reside on the Azure server. I would want it to be on the developer's own machine. It looks like you have two places for the connection string to do the job of three things. / comments
No. I recently posted another question where I wanted the connection string for new users of the project to point to the correct database. If it did not, it would create a bit of a mess as they w...
Azure database, Default Connection String, Shadow Database
My development database is an Azure database. I need to make sure that all developers use that database so I have set that as the default connection string. When the project attempts to utilize a...
Work-around. If you edit the Initial Catalog through the project properties display it works. / comments
Work-around. If you edit the Initial Catalog through the project properties display it works.
Sorry, now I am having another problem. On the second PC, it is constantly giving me the "Change Connection" screen (See attached). When I attempt to specify the connection, by default it is putting the name of the project as the database name instead of what is specified in the default. After correcting, if I click "Test Connection" it works; however, when I click 'OK', it goes back to the "Change Connection" screen [image] Here is the Default Connection [image] Here is what shows when I attempt to Change Connection. The database name is not coming from the "Default Connection String" but instead, from the project name [image] / comments
Sorry, now I am having another problem. On the second PC, it is constantly giving me the "Change Connection" screen (See attached). When I attempt to specify the connection, by default it is p...
There was no <DefaultConnectionString> property .sqlproj file for my project. I assume that is not set automatically when you first build the project? I have set it now. / comments
There was no <DefaultConnectionString> property .sqlproj file for my project. I assume that is not set automatically when you first build the project? I have set it now.
Where does SQL Change Automation store the connection string to the development database
We want to make sure that two different users point to the same development database. I would expect that this be stored somewhere within the project and be picked up by our source control (GIT). ...