Comments
Sort by recent activity
So, to recap,
The SCA project handles propagation to both databases (project DB and Shadow DB) automatically for all migration scripts and programmable objects. The Offline Schema model is not deployed anywhere.
Therefore, I should not be using any USE <databasename> statements in the SCA project scripts, as this will break SCA's ability to deploy to both databases.
All I need to do now then, is to come up with a way for the Visual Studio T-SQL Editor to default to the correct database when connecting, and all is well.
Does all of the above make sense? Thanks, SB / comments
So, to recap,
The SCA project handles propagation to both databases (project DB and Shadow DB) automatically for all migration scripts and programmable objects. The Offline Schema model is not de...
Also, are the Pre and Post Deployment scripts excluded from the above rule? In other words, are they not deployed automatically to both databases? / comments
Also, are the Pre and Post Deployment scripts excluded from the above rule? In other words, are they not deployed automatically to both databases?
Also, the problem was that there were scripts that were NOT running on the Shadow database. So I had to find a way to include the scrips, not exclude them. / comments
Also, the problem was that there were scripts that were NOT running on the Shadow database. So I had to find a way to include the scrips, not exclude them.
The scripts that were having trouble running on the Shadow DB were not migrations...they were object scripts, such as the schemas. / comments
The scripts that were having trouble running on the Shadow DB were not migrations...they were object scripts, such as the schemas.
So, does SCA handle applying ALL objects to both databases (the project DB and the Shadow DB) without me having to do anything to the files? Does it do this automatically for all programmable objects and migration scripts? And all other files are excluded? / comments
So, does SCA handle applying ALL objects to both databases (the project DB and the Shadow DB) without me having to do anything to the files? Does it do this automatically for all programmable obje...
Of course, right after I posted I found a solution....I changed the 3 Foreign Key columns on the table to 'Foreign Key Manual' and the time is back down to a few seconds. Before it was on 'Foreign Key Automatic' and it was taking 20-25 minutes. / comments
Of course, right after I posted I found a solution....I changed the 3 Foreign Key columns on the table to 'Foreign Key Manual' and the time is back down to a few seconds. Before it was on 'Foreign...
More specifically, it appears that I have 1 table that is taking much longer to generate than all the others, and I can't find the reason why. I see that on another table we are inserting thousands of rows every few seconds but on this table it's more like dozens of rows.
Both tables are inserting 20 million rows, have several FKs, and they have similar rowsizes (626 bytes for the faster table and 778 for the slower). Any ideas? / comments
More specifically, it appears that I have 1 table that is taking much longer to generate than all the others, and I can't find the reason why. I see that on another table we are inserting thousand...
Let me clear up one thing: SQL Source Control decrypts the object and shows it decrypted on the 'Commit changes' page. However, since I am using SSMS to develop, how can I decrypt the object when I want to change it? I don't see a way to decrypt the object in SSMS Object Explorer so that I can make changes to it. What is recommended in this case?
Thanks, / comments
Let me clear up one thing: SQL Source Control decrypts the object and shows it decrypted on the 'Commit changes' page. However, since I am using SSMS to develop, how can I decrypt the object when...
Any resolution on this? I am having this problem right now, and only trying to generate 1,000 rows. / comments
Any resolution on this? I am having this problem right now, and only trying to generate 1,000 rows.
I am still getting this error using Git. Any fixes/workarounds? / comments
I am still getting this error using Git. Any fixes/workarounds?