User profile for Andrew P

Thanks for contacting us! I recommend that you install the visual J# runtime as described here https://documentation.red-gate.com/disp ... +not+found I have followed up with you via email in case you have any questions or issues with that, please let me know! Warmly, / comments

Thanks for contacting us! I recommend that you install the visual J# runtime as described here https://documentation.red-gate.com/disp ... +not+found I have followed up with you via email in case y...

0 votes

Hey JHH, Thanks for contacting us and sorry you are having this issue! I have logged this as feature request SE-694, note that no work is planned on SQL Multi Script in the short term, but your request will be there when they pick up work again. I have followed up with you via email if you have any other questions or issues. Warm Regards, / comments

Hey JHH, Thanks for contacting us and sorry you are having this issue! I have logged this as feature request SE-694, note that no work is planned on SQL Multi Script in the short term, but your req...

0 votes

Hello, Jeff and I troubleshot this and the fix was to update to SQL Source Control 4.1.8.41 standard. If you have an issue similar to this, and updating does not solve the issue, please shoot us an email at support@red-gate.com It was good working with you Jeff! Best Regards, / comments

Hello, Jeff and I troubleshot this and the fix was to update to SQL Source Control 4.1.8.41 standard. If you have an issue similar to this, and updating does not solve the issue, please shoot us an...

0 votes

Hey kmh090, Thanks for posting and sorry for the frustration! For anyone else who reads this, we solved it by going to SQL Prompt -> Options -> Qualification and making sure that the "qualify object names with aliases" option is checked. It was a pleasure working with you and hope you have a great New Years! Warmly, / comments

Hey kmh090, Thanks for posting and sorry for the frustration! For anyone else who reads this, we solved it by going to SQL Prompt -> Options -> Qualification and making sure that the "qualify objec...

0 votes

Hey Opc, Thanks for the update! SQL Prompt does not underline errors, that is done directly by SSMS' Intellisense. Sometimes these errors keep Prompt from doing something (like executing a single line), but that is because we take the error as something that needs to be fixed. In this case it looks like SSMS is not detecting that the #tmp table has the columns "id" and "name" even though it was created directly above. If you put the table (#tmp) name in front of the column names (qualifying it), the tool will properly suggest a column. If you try to use "Qualify Object names" it will error out because there are two tables that have the "id" and "name" column names and it will not (and cannot) guess which one you mean. I hope that helps! Warm Regards, / comments

Hey Opc, Thanks for the update! SQL Prompt does not underline errors, that is done directly by SSMS' Intellisense. Sometimes these errors keep Prompt from doing something (like executing a single l...

0 votes

The easiest thing to do in this instance, is to grant the User Execute permissions on Tempdb, or on that specific object. Best, / comments

The easiest thing to do in this instance, is to grant the User Execute permissions on Tempdb, or on that specific object. Best,

0 votes

Hey acrawford, Thanks for posting! You can change the development model by unlinking and relinking, during the relink make sure to set the development model to shared. Prior to unlinking, make sure you commit all items that you would like to commit, then do the unlink and relink. I have also followed up with you via email in case you have any further questions or issues. Hope you have a great weekend! Andrew Product Support Engineer Red Gate Software / comments

Hey acrawford, Thanks for posting! You can change the development model by unlinking and relinking, during the relink make sure to set the development model to shared. Prior to unlinking, make sure...

0 votes

Hey Acrawford, Thanks for the update and sorry about that! I did not realize it initially but GIT can only be used in Dedicated mode. This is because it assumes that you will be working with other teammates who will be committing to the remote repository while you commit and get from your local working folder/repository (then push the changes up to the remote server). Working in Dedicated mode just allows you to Get from the local repository and Pull from the remote repository- in Shared you would not have that option. Is there any reason why you would not want to have that capability? Warm Regards, / comments

Hey Acrawford, Thanks for the update and sorry about that! I did not realize it initially but GIT can only be used in Dedicated mode. This is because it assumes that you will be working with other ...

0 votes

Thanks for posting! Currently there is no way to use Multi Script as the default Editor for SQL Data Compare and SQL Compare, but I think that is a great feature request for our User Voice forums located here https://redgate.uservoice.com/forums/141379-sql-compare Thank you for the great suggestion and I will follow up with you via email if you have further questions or issues! Warm Regards Andrew Product Support Engineer / comments

Thanks for posting! Currently there is no way to use Multi Script as the default Editor for SQL Data Compare and SQL Compare, but I think that is a great feature request for our User Voice forums l...

0 votes

Hey Seanwow, Thanks for posting and I apologize for the frustration, I raised this with our devs and they have been helpful in figuring out where the issue lies. We have been working together on this and here is a brief paraphrase of what we have thus far: SOC does support server side TFS 2015, as long as Team Explorer 2013/2012/2010 is installed alongside Source Control on the client machine. It does not support Team Explorer 2015 and currently there are no plans to add support for it. https://documentation.red-gate.com/disp ... e+selected The issue with this instance is that his TFS 2015 instance has a comment policy. Source Control can have issues with policies so he has to use the #ignorepolicies flag every time he commits. There's a more global workaround so you don't have to enter the comment each time- you can add IgnoreTfsPolicies to the engine options file (C:Users%UserName%AppDataLocalRed GateSQL Source Control 4RedGate_SQLSourceControl_Engine_EngineOptions.xml), with a value of True (<IgnoreTfsPolicies> True </IgnoreTfsPolicies>) That's only skirting round the problem though. TFS Policies are interesting to work with. Any policies you wish to use need to be correctly installed on both the server and the client. The error you are getting: The policy assembly 'Microsoft.TeamFoundation.VersionControl.Controls, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not registered Suggests it's not installed correctly somewhere. It might be that when you (tried to) connect to 2015, it updated / registered a newer version of that assembly which now stops it working. We tried manually registering the assembly, but it's not one where that seems to work. It seems the same error could occur via VS anyway, again in relation to incompatible versions, so it might be worth it for you to remove and re-add the policy: http://blogs.msdn.com/b/buckh/archive/2 ... olicy.aspx Warm Regards, Andrew Product Support Engineer / comments

Hey Seanwow, Thanks for posting and I apologize for the frustration, I raised this with our devs and they have been helpful in figuring out where the issue lies. We have been working together on th...

0 votes

How can we help you today?

Andrew P

Comments