Comments
Sort by recent activity
Thanks for your post.
I'm not sure what are plans are to support VS 11, but we're unlikely to officially support it before it's RTM.
As far as I know, you need to install a Team Explorer client to work with TFS, so you'll need to install one if VS 11 doesn't come with one by default.
Let us know how you get on after installing the client, it would be interesting to see if you have any other issues or not. / comments
Thanks for your post.
I'm not sure what are plans are to support VS 11, but we're unlikely to officially support it before it's RTM.
As far as I know, you need to install a Team Explorer client to ...
Thanks for your post.
I'm afraid table valued types are not fully supported in SQL Prompt 5.
We have an internal case open for this, but I can't give you an estimate on when you can expect full support. For your reference the internal tracking code for this is SP-2142.
It might help if you log a suggestion on our uservoice site, as the more popular suggestions are more likely to be implemented.
Sorry I can't be of more help. / comments
Thanks for your post.
I'm afraid table valued types are not fully supported in SQL Prompt 5.
We have an internal case open for this, but I can't give you an estimate on when you can expect full sup...
Thanks for your post.
I'm afraid we don't offer any pre-filtering in SQL Compare because of the way we need to register the whole schema to understand all the object dependencies.
However, you have not been the first person to suggest the idea, so I've added you as another vote for SC-2471.
You might like to also suggest the idea on our uservoice site as this is a bit more visible and other users can vote on the idea too.
You may also like to vote for the suggestion to make SQL Compare 64bit, as this would probably help with the memory issues you're finding. / comments
Thanks for your post.
I'm afraid we don't offer any pre-filtering in SQL Compare because of the way we need to register the whole schema to understand all the object dependencies.
However, you have...
Thanks for your post.
At what point are you seeing this error?
Does the account that you're using have enough permissions to install the framework and set the database to trustworthy? / comments
Thanks for your post.
At what point are you seeing this error?
Does the account that you're using have enough permissions to install the framework and set the database to trustworthy?
You can get it from 'help > Check for updates'.
CFU is likely to be the first place you can get patches, as the release process to make it into the bundle takes a little longer. / comments
You can get it from 'help > Check for updates'.
CFU is likely to be the first place you can get patches, as the release process to make it into the bundle takes a little longer.
Thanks for your post.
This has actually been fixed in the next update (10.2); which should be released tomorrow.
Our internal tracking code for this is SC-5128 / comments
Thanks for your post.
This has actually been fixed in the next update (10.2); which should be released tomorrow.
Our internal tracking code for this is SC-5128
Have you had a chance to try SQL Compare 10.2 yet? / comments
Have you had a chance to try SQL Compare 10.2 yet?
Thanks for your post.
This issue has actually been fixed in the next SQL Compare update. We are doing exactly what you suggested in your proposal.
As you know, SQL Azure complains if you try to put data in a table without a clustered index. We solved this problem if the index was a PK, but forgot to use the same behaviour for other unique indexes.
The fix SC-5128 should be available tomorrow through 'check for updates' / comments
Thanks for your post.
This issue has actually been fixed in the next SQL Compare update. We are doing exactly what you suggested in your proposal.
As you know, SQL Azure complains if you try to put...
10.2 is is available now through 'check for updates' Does this fix the problem? / comments
10.2 is is available now through 'check for updates' Does this fix the problem?
Hi Matt,
SQL Compare suffers from the same problems as SQL Source Control, which I briefly described in your other thread. / comments
Hi Matt,
SQL Compare suffers from the same problems as SQL Source Control, which I briefly described in your other thread.