User profile for ScottA

I'm having the same problem and have had to turn off code analysis. repro steps: type "exec spMyStoredProcedure" (leaving out the dbo.) This will trigger an issue "Schema name for procedure is not specified" as i didn't put in dbo. Right click the spMyProcedure (to say do script as alter), Will hang and the issue icon will flicker. / comments

I'm having the same problem and have had to turn off code analysis. repro steps:type "exec spMyStoredProcedure" (leaving out the dbo.)This will trigger an issue "Schema name for procedure is not sp...

0 votes

Bump! Can this item be made a priority? I'm looking forward to some of the new features since 3.1 and am completely blocked from installing the new version with this error (the 'keep the selections when navigating away and coming back to the commit window' one alone should save me quite a lot of time) As previously mentioned am happy to assist in diagnosing the issue if you guys can't reproduce it. Also - Sproatba, I'm not using any (non redgate) SSMS plugins and haven't had any installed since my last rebuild a while ago. Cheers, / comments

Bump! Can this item be made a priority? I'm looking forward to some of the new features since 3.1 and am completely blocked from installing the new version with this error (the 'keep the selections...

0 votes

I just upgraded to 3.2 thinking this might have been sorted but the issue still remains in this build. I'll need to reinstall 3.0 again to now as I need this working but am happy to send through any debug info / run any tests to get this sorted ASAP. I am also using SQL 2008 R2, 64bit windows 8. Cheers, / comments

I just upgraded to 3.2 thinking this might have been sorted but the issue still remains in this build. I'll need to reinstall 3.0 again to now as I need this working but am happy to send through an...

0 votes

Hi Vic, I downgraded to 3.0 which brought it all back for me. / comments

Hi Vic, I downgraded to 3.0 which brought it all back for me.

0 votes

I've just had this problem also. Error comes up in SQL 208 R2 and 2012 management studio when loading. The event log has a lot of the following from the source "SQL Source Control 3" and "SQL Test 1" #QEc.#mRA #1:Failed to load assembly RedGate.SQLPrompt.SSMSUIfw4.resources.resources, Version=5.3.6.28, Culture=en-US, PublicKeyToken=7f465a1c156d4d57 Broke my golden rule of doing an upgrade when I actually needed to do a UAT update and needed to generate some scripts, it's a testament to Redgate though as I'm so used to their upgrades working flawlessly that i didn't give it a second thought! / comments

I've just had this problem also. Error comes up in SQL 208 R2 and 2012 management studio when loading. The event log has a lot of the following from the source "SQL Source Control 3" and "SQL Test ...

0 votes

ComparisonOptions file management

Hi Guys, When SQL source control starts to compare the linked database to source control can you get it to look for an updated ComparisonOptions file in source control and check it out and use it? ...

1 follower 1 comment 0 votes

By 'manage across developers' I mean manage the deployment script creation / update process across several developers. ie: one developer creates the script, submits it - everyone sees it and knows to use it when needing a script to do a deployment. I'm sure the migration scripts when applied by SQL Compare or using Source Control's getLatest would be in a transaction my issue is that all of the production systems we deal with aren't able to be hooked up to our development machines and therefore we need to run the scripts manually on the production servers. We could use migration scripts through SQL compare / source control to perform upgrades internally between DEV and QA but I've found it's best to deploy out to QA with the same scripts / process you would use in production as that way any issues with scripts are also picked up in advance. As the migration scripts are a seperate item in source control it would be ideal if the scripts created were standalone production ready scripts which also included any data changes checked in to source control. Then I suppose any data migration bits could be added to the end of the script and you're good 2 go. This would be a lot cleaner and easier to manage as it's a tab in the source control tool where as currently I'd need to use the two compare tools to generate seperate scripts and then check them in to a random source control folder which people need to know to look in. What I meant about the comparison settings is the stuff like 'ignore collations' which you can now set in the comparison.xml file for SQL Source control and also set in the options when using SQL compare. I can see that the migration script functionality doesn't really fit in with what I'm trying ot do at the moment and we can certainly use the other tools to do this, I would have thought that most people would be in the same boat in regards to not being able to hook up production systems to source control, espeially if they are managing products with a large install base. Is there an easier way to manage this through your toolset that I'm missing? Cheers, / comments

By 'manage across developers' I mean manage the deployment script creation / update process across several developers. ie: one developer creates the script, submits it - everyone sees it and knows ...

0 votes

Migration scripts -Transaction support/Static Data changes?

I've been looking at using the migration script functionality instead of using the seperate structure / data comparison tools as this would help us manage the deployment scripts across developers q...

2 followers 3 comments 0 votes

Comparing two Source control versions

I've come across an issue where data compare isn't picking up data changes when comparing two source control revisions where there have been structural changes involved. Example: I have a table wit...

1 follower 1 comment 0 votes

How can we help you today?

ScottA

Activity overview