Comments
Sort by recent activity
I'm having the same problem. Just upgraded to 3.3.1.2410 and no search results when searching for a field that I know appears multiple times in our database. Any help is much appreciated. / comments
I'm having the same problem. Just upgraded to 3.3.1.2410 and no search results when searching for a field that I know appears multiple times in our database. Any help is much appreciated.
Got it. Thanks. / comments
Got it. Thanks.
Is it possible to bypass the initial migration script and test a change to my database? The necessary database objects were created successfully in my shadow database. The errors I'm getting now are referencing objects that have already been created and cannot be recreated. / comments
Is it possible to bypass the initial migration script and test a change to my database? The necessary database objects were created successfully in my shadow database. The errors I'm getting now ar...
I haven't made any changes to the target yet. I created a new database project based on an existing database. When I imported the existing database, the migration script was automatically generated to create the database objects that already existed, but some of the views in the database reference fields in tables that no longer exist. I ran the script repeatedly to find all the missing objects in the database and commented out objects that no longer exist. When I got closer to the end of the migration script and clicked the Deploy button, I started getting messages that referenced the line numbers in the file path above instead of referencing the line number in Visual Studio. This is a SQL Source Control project and I am trying to connect to a database project from SSDT/Visual Studio in TFS. / comments
I haven't made any changes to the target yet. I created a new database project based on an existing database. When I imported the existing database, the migration script was automatically generated...