Comments
Sort by recent activity
Bill, It may be worth noting that SQL Prompt will allow you to recover those scripts. In version 4 you can hover over the object name and click the yellow tooltip. The script pane will come up with the complete script.
If you are using the SQL Prompt 5 EAP you can right click on the object name and "Script object as alter", which avoids hitting this (and several other) bugs in SSMS's script object as alter. / comments
Bill, It may be worth noting that SQL Prompt will allow you to recover those scripts. In version 4 you can hover over the object name and click the yellow tooltip. The script pane will come up w...
Another option is to attach the Visual Studio debugger and put exception catch on only for InvalidOperationException.
[Ctrl + Alt E] / comments
Another option is to attach the Visual Studio debugger and put exception catch on only for InvalidOperationException.
[Ctrl + Alt E]
Assembly.CodeBase is still set.
string codeBase = assembly.CodeBase;
string localPath = new Uri(codeBase).LocalPath;//NOTE: assembly.Location will often be "" because of {SA}
I'm not sure if this behaviour is guaranteed in {SA} / comments
Assembly.CodeBase is still set.
string codeBase = assembly.CodeBase;
string localPath = new Uri(codeBase).LocalPath;//NOTE: assembly.Location will often be "" because of {SA}
I'm not sure if this b...
Hey peter. Sorry again about the problem, we're working on fixing it, but I for now I'm just going to flesh out the work around. Once you've committed the assembly to source control we are unable to show the tab, but if it never goes into source control (or we cunningly delete it) then the tab will still work. That means that you can carry on trying out the product by never committing the assembly.
In order to delete the assembly you can
- Delete the assemblies sql file using your normal source control client and commit
- You then need to go and update your WorkingBase folder manually using your source control client. If you look in C:\Users\<whoever>\AppData\Local\Red Gate\SQL Source Control 1\WorkingBases for the file you just deleted in source control, and then update the Assemblies directory containing it the file should disappear
- If you then restart SSMS the tab should now load without error, showing the Assembly as an Add on the commit tab. / comments
Hey peter. Sorry again about the problem, we're working on fixing it, but I for now I'm just going to flesh out the work around. Once you've committed the assembly to source control we are unabl...
The product should work with that configuration. Since we make frequent connections to SVN you will have to use a tool such as Pageant to keep the key available for SQL Source Control.
If you run pageant ( available from the putty page here http://www.chiark.greenend.org.uk/~sgta ... nload.html ), then right click on its system tray icon and "Add Key" then the product should be able to authenticate with your subversion server as normal. / comments
The product should work with that configuration. Since we make frequent connections to SVN you will have to use a tool such as Pageant to keep the key available for SQL Source Control.
If you run ...
Thanks for reporting the problem. I've managed to reproduce it locally, and raised an issue (SOC-1261). There's a problem with our reading in the collation from the script file. It gets written to source control correctly, but read back wrong. I'll have a look at a fix and try and get it into the next private build. / comments
Thanks for reporting the problem. I've managed to reproduce it locally, and raised an issue (SOC-1261). There's a problem with our reading in the collation from the script file. It gets written ...
Hi,
Thanks for reporting the issue. The error indicates that there are two files under the directory the database is linked to which contain "Create table [dbo].[XXXXXXX]". One case this can happen is where you link to SomeFolder, and then copy it into itself, so you end up with
SomeFolder
SomeFolder\Tables
SomeFolder\Tables\dbo.XXXXXX.sql
SomeFolder\OldVersion
SomeFolder\OldVersion\Tables
SomeFolder\OldVersion\Tables\dbo.XXXXXX.sql
Is it likely you have two copies of the create table file in source control? If so, can you see why? If you could email me a zip of the folder from source control ( to my username @red-gate.com) I should be able to see more of what's going on. / comments
Hi,
Thanks for reporting the issue. The error indicates that there are two files under the directory the database is linked to which contain "Create table [dbo].[XXXXXXX]". One case this can happ...
luan_au,
Sorry for the delay in replying. Thanks for submitting the problem you had, both here and from within the product.
The problem you have seen occurs when the working copy of the database contains a statement such as
EXEC sp_addrolemember N'role_name', N'SunBrowser'
GO
But not the corresponding
CREATE USER SunBrowser
statement.
We are working on a fix for this issue (SOC-845). You should be able to carry on working if you SVN update (using tortoise, or any other SVN client) the Security\Users and Security\Schemas folders in your working base in order to make sure that the create user statement exists. I will PM you with the precise details for your case. / comments
luan_au,
Sorry for the delay in replying. Thanks for submitting the problem you had, both here and from within the product.
The problem you have seen occurs when the working copy of the database ...
You can search UserVoice by typing in the 'Suggest a new feature or enhancement'. It searches as you type, in order to try and reduce the number of duplicate entries. I agree it's not the most obvious behaviour! / comments
You can search UserVoice by typing in the 'Suggest a new feature or enhancement'. It searches as you type, in order to try and reduce the number of duplicate entries. I agree it's not the most o...
Hi,
I've just had a quick look at the work around for this.
You should be able to get back up and running again if you:
- Unlink the database from source control
- Make sure the DB is in same state as source control (sounds like this should be true already)
Then in source control explorer:
- Delete RedGate.ssc
- Check in
- ReCreate RedGate.ssc (don't undo the delete)
- Check in
Now link to source control. if you go to the tabs you should see a long spinny and be good to go.
Let me know if that works for you.
We're still looking at fixing the underlying bug so this faff isn't required, but we'd really like you to keep trying the product. / comments
Hi,
I've just had a quick look at the work around for this.
You should be able to get back up and running again if you:
- Unlink the database from source control
- Make sure the DB is in same state...