Comments
Sort by recent activity
#2 is burning issue. Please guide us to resolve this. / comments
#2 is burning issue. Please guide us to resolve this.
Hi Jessica, - Can you please click on the option at the bottom of the error window to send in a report and send one in with your email address included (the one used to log into the forum)? Error message is empty. However, I solved the issue by editing create test class procedure. It was failing at CREATE SCHEMA step. Just changed it to EXEC ('CREATE SCHEMA ' + @QuotedClassName + ' AUTHORIZATION [dbo]'); - Can you please check your log files in %localappdata%\Red Gate\logs\SQL Test 4 for any related errors? - Can I also please check which Azure authentication mode you are using? I am using AAD Integrated method to connect to azure sql. / comments
Hi Jessica, - Can you please click on the option at the bottom of the error window to send in a report and send one in with your email address included (the one used to log into the forum)?Error me...
Same Issue and Fix. Uninstalled Dependency tracker. / comments
Same Issue and Fix. Uninstalled Dependency tracker.
@way0utwest I posted the test code block with all fake names / comments
@way0utwest I posted the test code block with all fake names
Thanks for the reply, Sergio. I am wondering if there is alternate so I don't have to copy the script in migration script. Its definitely an additional task that I like to avoid if its possible. / comments
Thanks for the reply, Sergio. I am wondering if there is alternate so I don't have to copy the script in migration script. Its definitely an additional task that I like to avoid if its possible.
Good news that this issue appears to be have magically gone now. Bad news is no clue what happend but I am suspecting my fresh reinstallation of SCA plugin did something. Bug again, surprisingly with no changes except that I closed and reopned solution multiple attempts. / comments
Good news that this issue appears to be have magically gone now. Bad news is no clue what happend but I am suspecting my fresh reinstallation of SCA plugin did something. Bug again, surprisingly wi...
All it has is this single empty json file. [image] / comments
All it has is this single empty json file.
Hi Sergio, I can't share project but I can share logs. But the 9 line log file doesn't have much information. Are there any detailed logs created somewhere else? -- Log (changed server name and couple of table names)
...stionMPExclusion]
Creating [dbo].[MPCAS]
Creating primary key [PK_MPCAS] on [dbo].[MPCAS]
Creating [dbo].[GetMPF]
Creating [dbo].[UserIdIssuer]
Creating primary key [PK_UserIdIssuer] on [dbo].[UserIdIssuer]
Creating [dbo].[GetNewUserId]
Msg 2714, Level 16, State 3, Server X12-NG-XXXX022D\LOCALDB#D59D025F, Procedure GetNewUserId, Line 1
There is already an object named 'GetNewUserId' in the database. Baseline script marked as deployed[image] Let me know if you need any further details
/ comments
Hi Sergio,I can't share project but I can share logs. But the 9 line log file doesn't have much information. Are there any detailed logs created somewhere else?-- Log (changed server name and coupl...
Hi Sergio, I don't think that's the issue because I can confirm that the baseline script was marked as deployed already. Two other important points which I could not understand. I created a new folder and pulled the code from repo, that did not gave this issue. Same code without any change. That's first. Second, why the error log is showing different server name and db name which I was haven't pointed to. I connected to on-prem sql server and the error log was showing azure server name which I didn't even connected. / comments
Hi Sergio,I don't think that's the issue because I can confirm that the baseline script was marked as deployed already. Two other important points which I could not understand. I created a new fold...
Post scripts sounds good. But it looks like its not an ideal solution in our case because we have multi-tenent db. So till we move final data to prod, we may have to reload the data multiple times in lower environments and we won't touch it once released to prod. So, after releasing to prod, it's unnecessary to check if it's loaded or not (from post deployment script) So the need is to simply run the script only when data changes. Like I mentioned in my initial post, are there any risks of manually changing the migration id or delete old script and create a new one? Only issue I see here is that the migration logs will have migration ids which won't be found in the SCA solution. / comments
Post scripts sounds good. But it looks like its not an ideal solution in our case because we have multi-tenent db. So till we move final data to prod, we may have to reload the data multiple times ...