Activity overview
Latest activity by pbarry
Hi,
I was just wondering if this feature (comparing system objects) was still on your list.
Thanks.
Patrick / comments
Hi,
I was just wondering if this feature (comparing system objects) was still on your list.
Thanks.
Patrick
Thank you!
P.S. I know it's way more difficult than just adding a checkbox. I was just referring to the fact that not everyone wants to compare "system objects".
Patrick / comments
Thank you!
P.S. I know it's way more difficult than just adding a checkbox. I was just referring to the fact that not everyone wants to compare "system objects".
Patrick
Hi!
I've been asking for this functionnality (comparing system objects) since 2004. I hope it makes the cut this time. Here are other reasons why I need to compare system objects:
* SOX compliance:
-> Making sure nobody changes system stored procedure
-> Making sure rights are what they should be on system objects
* Making sure patches have been applied on all servers
* Comparing the behavior of installing cumulative Service Packs on a server: for instance, if you install SP3a on SQLServer 2000 (no SP), you won't get the same results as installing SP3a on SQLServer 2000 SP2!
* And finally, we sometime change system stored procedures to correct problems not yet corrected by Microsoft (ex: msdb.dbo.sp_help_jobstep is missing a "ORDER BY" so job steps are sometime displayed in an incorrect order in Enterprise Manager)
Users might have requested that you ignore them, but just adding a checkbox on the options pages asking to "include system objects or not" is not that difficult ;-)
Otherwise, great product
Regards,
Patrick / comments
Hi!
I've been asking for this functionnality (comparing system objects) since 2004. I hope it makes the cut this time. Here are other reasons why I need to compare system objects:
* SOX complianc...
Hi!
Just to let you know that version 3.2.1.14 corrected my problems.
Thanks!
Patrick / comments
Hi!
Just to let you know that version 3.2.1.14 corrected my problems.
Thanks!
Patrick
Hi Ed and Brian,
thanks for the info. As for your offer Brian, I can wait for the release if it's not too far in the future. I just needed to know what was happening with this problem. Brian, I would really appreciate it if you could give me a time frame for the next release.
P.S. I have 2 theories on why we're having this problem:
1) SQL Server might be compressing information internally when it needs to change records from one page to another. That way, we get spaces in one database and not in the other one (or after doing an update).
2) Depending on the MDAC version installed, the SQL Server OLEDB driver might have a bug in it (or in the ADO.NET) and might be padding blanks when it should not. For instance, it the driver uses the "ANSI_PADDING" setting at the server level (or database level or connection level) instead of the one at the table level, we would be getting different results from different servers (or databases).
Unfortunately, I haven't had the time to test all these scenarios to confirm anything.
Patrick / comments
Hi Ed and Brian,
thanks for the info. As for your offer Brian, I can wait for the release if it's not too far in the future. I just needed to know what was happening with this problem. Brian, I...
Hi!
Has there been any advance on that matter? We rely a lot on SQL Data Compare to make sure everything is ok before we go to production and I must say that this "bug" (or at least it's what it seems to be) creates a lot of mistrust in SQL Data Compare from our QA people. And I would really like to tell them that it's being fixed in the next release...
Patrick / comments
Hi!
Has there been any advance on that matter? We rely a lot on SQL Data Compare to make sure everything is ok before we go to production and I must say that this "bug" (or at least it's what it s...
Hi!
I have the same problems so I'm very interested in knowing if the new version corrects the problem.
Thanks. / comments
Hi!
I have the same problems so I'm very interested in knowing if the new version corrects the problem.
Thanks.