Comments
Sort by recent activity
Although SQL Source Control will work with SQL Server 2012 and SSMS 2012, it still has trouble parsing functions that are new in SQL Server 2012. We're working on supporting the new functions, but for the time being there's not really much I can suggest here - we don't have a version of SQL Source Control that can handle this syntax right now. Sorry! / comments
Although SQL Source Control will work with SQL Server 2012 and SSMS 2012, it still has trouble parsing functions that are new in SQL Server 2012. We're working on supporting the new functions, but ...
We've had a couple of other instances of this reported in the past, and it seems to occur when access to the server is attempted by an account where there's no associated user. In the case of one customer, it's where NT AUTHORITY\System was accessing the server, but there was no associated SQL Server user to that Windows login. Once one had been created, the problem went away. So to begin with, ensure that any Windows accounts accessing the server have a valid associated SQL Account. / comments
We've had a couple of other instances of this reported in the past, and it seems to occur when access to the server is attempted by an account where there's no associated user. In the case of one c...
Right, OK. Glad to hear it cleared up - let me know if it starts happening again, and I'll try and get to the bottom of it! / comments
Right, OK. Glad to hear it cleared up - let me know if it starts happening again, and I'll try and get to the bottom of it!
Hmm. Are lots of users getting these errors? Does unlinking and relinking the database/s sort anything out? / comments
Hmm. Are lots of users getting these errors? Does unlinking and relinking the database/s sort anything out?
Ah, right, great. Glad to hear that sorted it out, although I'm not sure why it happened in the first place! Let us know if it crops up again or if there's anything else I can help with. / comments
Ah, right, great. Glad to hear that sorted it out, although I'm not sure why it happened in the first place! Let us know if it crops up again or if there's anything else I can help with.
I can't figure out how this has happened - I've installed SQL Prompt 4 for testing, and it gives me the keyboard shortcut Ctrl+K Ctrl+Y. That shouldn't be configurable. Did it previously display Ctrl+K Ctrl+Y, or has it always displayed Ctrl+.Ctrl+. for you? Have you tried reinstalling? / comments
I can't figure out how this has happened - I've installed SQL Prompt 4 for testing, and it gives me the keyboard shortcut Ctrl+K Ctrl+Y. That shouldn't be configurable. Did it previously display Ct...
Can I check the exact version of SQL Prompt you're using? / comments
Can I check the exact version of SQL Prompt you're using?
Actually, SQL Compare doesn't support SQL 2000 any more either, although it still just about works. SQL Source Control has never supported SQL 2000, though, and it's because of the way we collect trace information, not because of the Compare engine - the way we collect trace information is fundamentally incompatible with SQL 2000, so it's unlikely it'll ever be supported with SQL Source Control. Sorry! / comments
Actually, SQL Compare doesn't support SQL 2000 any more either, although it still just about works. SQL Source Control has never supported SQL 2000, though, and it's because of the way we collect t...
The last version of SQL Compare to officially support SQL Server 2000 was version 9.xx - it looks like that page is outdated in that aspect. The requirements page here: http://www.red-gate.com/products/sql-de ... quirements doesn't list SQL 2000, as you can see.
Really what that means is that we've stopped testing SQL Compare with SQL Server 2000 - SQL Compare 10 still works, as far as I'm aware, with SQL Server 2000, but there may be SQL 2000-specific bugs, and since we don't test against it, those could make it into release.
If you want to use SQL Compare with SQL 2000 databases, version 10 will probably work, and if it doesn't version 9.5 is available for download here: http://www.red-gate.com/supportcenter/G ... d_versions
Hope that helps! / comments
The last version of SQL Compare to officially support SQL Server 2000 was version 9.xx - it looks like that page is outdated in that aspect. The requirements page here: http://www.red-gate.com/prod...
I'm afraid SQL Source Control doesn't actually support SQL Server 2000 - if you can get it working that's great, but we don't guarantee anything, and I know some features won't be too happy with it. Sorry! / comments
I'm afraid SQL Source Control doesn't actually support SQL Server 2000 - if you can get it working that's great, but we don't guarantee anything, and I know some features won't be too happy with it...