Comments
Sort by recent activity
Same problem when upgrading from 5.0 to 5.1 -- did you or anyone else find a resolution? / comments
Same problem when upgrading from 5.0 to 5.1 -- did you or anyone else find a resolution?
Follow up--it's been a week and have not experienced the error. I'll chalk it up to file system contention at this point unless I see it again. / comments
Follow up--it's been a week and have not experienced the error. I'll chalk it up to file system contention at this point unless I see it again.
No, nothing was installed on that server in the past several weeks. I've adjusted my backup schedules so that transaction log backups are not being run during that time, to see if that may reduce file system contention. Since doing that, I've not seen the error. I'll check back in after a few days. Thanks / comments
No, nothing was installed on that server in the past several weeks. I've adjusted my backup schedules so that transaction log backups are not being run during that time, to see if that may reduce f...
Ok...thanks for the response. I still don't know why the changes wouldn't save, but after rebooting, now it works--maybe some kind of goofiness with the write permissions on that registry key or something....
Thanks,
Jason / comments
Ok...thanks for the response. I still don't know why the changes wouldn't save, but after rebooting, now it works--maybe some kind of goofiness with the write permissions on that registry key or so...
Yes, but I hadn't selected v2.0 -- my fault.
(see below for: Version Information: Microsoft .NET Framework Version:1.1.4322.2490; ASP.NET Version:1.1.4322.2494 )
I didn't see that in the installation steps. May I suggest placing a sentance on http://www.red-gate.com/supportcenter/C ... M_UsingIIS under the heading "For IIS 6" under #3 which says something to this effect:
h. Navigate to the ASP.NET tab and ensure the version selected is 2.0.50727.
Thanks for the response! / comments
Yes, but I hadn't selected v2.0 -- my fault.
(see below for: Version Information: Microsoft .NET Framework Version:1.1.4322.2490; ASP.NET Version:1.1.4322.2494 )
I didn't see that in the installati...
Thank you...that fixed my issue! / comments
Thank you...that fixed my issue!
I just came on the forums specifically to request this--it would be great if SQL Compare would also just allow you to click a loaded snapshot or even DB structure that was just read in for comparison purposes and generate SQL Doc documentation from it. / comments
I just came on the forums specifically to request this--it would be great if SQL Compare would also just allow you to click a loaded snapshot or even DB structure that was just read in for comparis...
I just upgraded using your link and confirmed that the problem is fixed with this update. Like an idiot, I did that before documenting the issue with screen shots, so if you think they'll be useful, I guess I could try to downgrade and reproduce.
The version I was on that exhibited the problem is: 8.1.0.360. Checking for updates doesn't show any available, but I do see the OP was on 8.2 already.
Let me know--if you'd like the screen shots, I'll downgrade and put it together for you. If not, just know that that version has a problem and the latest does not.
Thanks,
Jason / comments
I just upgraded using your link and confirmed that the problem is fixed with this update. Like an idiot, I did that before documenting the issue with screen shots, so if you think they'll be useful...
I'm having the same issue as the OP. Steps to reproduce are:
CREATE TABLE Test (
ColA int NOT NULL,
ColB int NOT NULL,
IsObsolete bit NOT NULL
) ;
CREATE UNIQUE NONCLUSTERED INDEX ixTest_ColAColB_UN ON Test (ColA, ColB)
WHERE ColB IS NOT NULL AND IsObsolete = 0 ;
GO
The resulting Compare output shows:
-- Columns
CREATE TABLE [dbo].[Test]
(
[ColA] [int] NOT NULL,
[ColB] [int] NOT NULL,
[IsObsolete] [bit] NOT NULL
)
GO
-- Constraints and Indexes
CREATE UNIQUE NONCLUSTERED INDEX [ixTest_ColAColB_UN] ON [dbo].[Test] ([ColA], [ColB])
GO
This will have a major impact on synchronizing our dev and test environments. Please advise when a fix might be expected. If it helps any, SQL Doc catches the WHERE clause without a problem.
Thanks. / comments
I'm having the same issue as the OP. Steps to reproduce are:
CREATE TABLE Test (
ColA int NOT NULL,
ColB int NOT NULL,
IsObsolete bit NOT NULL
) ;
CREATE UNIQUE NONCLUSTE...