Comments
Sort by recent activity
Thanks for your post.
I haven't seen this specific error before, so can I ask exactly what you were doing at the time?
Is this when you're linking a new database to TFS, or are you using an existing repository?
Do you have the necessary permissions to check in and create files in the TFS repository?
Is it only when you're committing these schema permissions changes that you get the issue, or do you have a similar problem committing other objects as well? / comments
Thanks for your post.
I haven't seen this specific error before, so can I ask exactly what you were doing at the time?
Is this when you're linking a new database to TFS, or are you using an existin...
Thanks for your post.
I'm afraid there isn't a way to set SQL Compare to set extended properties with varchar instead of nvarchar. It sounds like a little bit of a hack anyway.
You could manually edit the sync script that SQL compare generates and remove the N' from the name parameter. i.e.
Output the sync script and then do a find and replace on
sys.sp_addextendedproperty @name=N'
to
sys.sp_addextendedproperty @name='
I hope this is helpful / comments
Thanks for your post.
I'm afraid there isn't a way to set SQL Compare to set extended properties with varchar instead of nvarchar. It sounds like a little bit of a hack anyway.
You could manually e...
Thanks for your post.
I'm afraid this isn't possible. There isn't a way to add any custom layout configurations, so if the option isn't there, then SQL Prompt 4 can't do it.
If you would like this layout option to be considered for a future version, I can add a feature request. / comments
Thanks for your post.
I'm afraid this isn't possible. There isn't a way to add any custom layout configurations, so if the option isn't there, then SQL Prompt 4 can't do it.
If you would like this ...
I've submitted a feature request SP-3536 for you. / comments
I've submitted a feature request SP-3536 for you.
Sorry for the delay.
Unfortunately we're not going to be able to support scripts that haven't been created using SQL Source control, or SQL Compare.
We may be able to read the scripts in, but we would end up writing them out to new files based on our own naming convention. This would end up loosing the history.
SQL Source control (and SQL Compare) only support scripts that are organised in a certain way. For example, if SSMS writes out objects like triggers to separate files, then we wouldn't be able to handle it.
We could add support for scripts created by SSMS, but as there are so many different configurations you can use, it would be a nightmare to support all of them. So far there doesn't seem to be much call for supporting SSMS scripts.
Sorry I can't really give you a workaround for this. / comments
Sorry for the delay.
Unfortunately we're not going to be able to support scripts that haven't been created using SQL Source control, or SQL Compare.
We may be able to read the scripts in, but we wo...
Thanks for your post.
It really depends on the format of the objects that reside in your existing repository.
If the scripts have been created using SQL Compare, then it may be possible to add the necessary config files to use the existing repository with SQL Source control. However, if the scripts have been created by another method, then it is probably unlikely that you can use SQL Source control with them.
Can you confirm how the current repository has been set up? / comments
Thanks for your post.
It really depends on the format of the objects that reside in your existing repository.
If the scripts have been created using SQL Compare, then it may be possible to add the ...
I was just about to get back to you about that.
I found exactly the same thing. Using the 'Geometry' keyword as a table alias, seems to confuse our parser. I've logged this as a bug (SC-4853)
I'll let you know when a fix is available. / comments
I was just about to get back to you about that.
I found exactly the same thing. Using the 'Geometry' keyword as a table alias, seems to confuse our parser. I've logged this as a bug (SC-4853)
I'll ...
Thanks for your post.
The problem might be that our own parser doesn't support some of the syntax in the file.
Would you be able to send me the file so I can check if this is the case?
"C:\Documents and Settings\rsboczkay\Local Settings\Application Data\Red Gate\SQL Source Control 1\WorkingBases\htbf31pg.i5f\Stored Procedures\dbo.GetMapPolygonsLowest.sql"
I've also send this in an email so you can reply to that rather then post the object here. / comments
Thanks for your post.
The problem might be that our own parser doesn't support some of the syntax in the file.
Would you be able to send me the file so I can check if this is the case?
"C:\Document...
Thanks for your reply.
That's the same list managed by the SVN cache. We load the list when you open the 'link' dialogue. If you manage the list using the method in the previous post and reopen the 'link' dialogue, you should see the results you're expecting. / comments
Thanks for your reply.
That's the same list managed by the SVN cache. We load the list when you open the 'link' dialogue. If you manage the list using the method in the previous post and reopen the...
Thanks for your post.
Can you let me know which list you need to clean up?
Is it the combo box you get in the Tortoise Repo-Browser you're referring to? If this is the one, the information is stored in the local SVN cache.
You can clear the URL History through the TortoiseSVN settings (Saved Data > URL History). Or you can use shift+delete on the repo-browser list to remove entries.
I hope this helps.
Let me know if you are enquiring about something else. / comments
Thanks for your post.
Can you let me know which list you need to clean up?
Is it the combo box you get in the Tortoise Repo-Browser you're referring to? If this is the one, the information is store...