InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 07:03:14 GMT20http://www.sqlservercentral.com/Forums/Topic341097-365-1.aspx<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>We used Lumigents AuditDB (Entegra at the time) in the past to capture log information in a db then replicate the information to another database.<SPAN style="mso-spacerun: yes"> </SPAN>Using this and we noticed that the log re-engineer was not 100%... very close though. </FONT></P><P class=MsoNormal style="MARGIN: 0in 0in 0pt"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p><FONT face="Times New Roman" size=3> </FONT></o:p></P><P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>We also used Log Explorer to view the questionable data and it could not correctly re-engineer the log information as well.<SPAN style="mso-spacerun: yes"> </SPAN>This only happened maybe 1 out of 10,000 transactions so it’s not very noticeable in Log Explorer but much easier to find in the AuditDB database. <SPAN style="mso-spacerun: yes"> </SPAN>We worked with support for about a year and eventually had to cancel the license because we needed 100% reliability.<SPAN style="mso-spacerun: yes"> </SPAN>Support was very knowledgeable and easy to work with but we just could not identify the reason for the failed re-engineering of the log transactions.<SPAN style="mso-spacerun: yes"> </SPAN>It’s been a couple of years so hopefully they have it fixed. <SPAN style="mso-spacerun: yes"> </SPAN>To their defense it is very complicated to restore SQL Server logs since they only store the net changes and not the complete column.<SPAN style="mso-spacerun: yes"> </SPAN>For example if you change “HAT” to “HATS”, the log file only stores “S”.</FONT></P><P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3></FONT> </P><P class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>David</FONT></P>Tue, 06 Mar 2007 08:02:00 GMTDavidSimpsonhttp://www.sqlservercentral.com/Forums/Topic341097-365-1.aspxWhat does it mean when it says that it supports SQL Server 2005 (Q3 2006)?Tue, 06 Mar 2007 06:16:00 GMTEd Bellhttp://www.sqlservercentral.com/Forums/Topic341097-365-1.aspx<P>Hi Ludovic,</P><P>Are you sure that it does not support SQL Server 2005?Yesterday my article on ApexSQL Log 2005 was published.I had mentioned in that article that its the only tool which supports 2005.In Lumigent Log explorer website,it is mentioned in the Platforms sections that it supports 2005(Q3 2006).I am not able to test it since its giving me some issues.I had only the evaluation version of Log explorer.So i wasnt sure whether it does support 2005 or not.Thanks fo rthe comments.</P><P>Regards,</P><P>S.Srivathsani</P><P> </P>Tue, 06 Mar 2007 03:28:00 GMTsrivathsani-296624http://www.sqlservercentral.com/Forums/Topic341097-365-1.aspxNice document, but do not forget to say that it does not support yet SQL Server 2005 ...Tue, 06 Mar 2007 01:16:00 GMTLudovic VIVIERhttp://www.sqlservercentral.com/Forums/Topic341097-365-1.aspxComments posted here are about the content posted at <A HREF="http://www.sqlservercentral.com/columnists/sSrivathsani/2846.asp">http://www.sqlservercentral.com/columnists/sSrivathsani/2846.asp</A>Tue, 30 Jan 2007 17:25:00 GMTsrivathsani-296624