This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi all, We're using LS 2.2 and I've run into a bit of a problem. We have a simple service we want to install on a server that only has SQL server 2000. Normally we use SQL server 2005, but our users don't want to upgrade to 2005 as they're upgrading directly to 2008 in a few months. I've created the table with the same schema I used in SQL server 2005. LS doesn't generate any errors in our logs, we simply don't get any data. I'd like to use the tracelogger to log the SQL queries to a file to start figuring out what's wrong. I know to add this attribute to my LS context,
Is it possible to integrate this logger with our existing log4net framework using log4net configurations?
Thanks, Todd |
|
|
Hi Todd, The latest nightly has some support for SQL 2000. Specifically it does not support paging due to the limitations of the SQL Server 2000. You won't be able to use the SQL2005 provider to work with it. Regarding SQL2000, I'd strongly suggest that you nudge your customer a little harder. SQL 2000 isn't even supported by Microsoft any longer and many products do not support it and it has been superseded by several versions. If you absolutely can't get a supported SQL Server then please do provide any feedback on issues you face and we can look at trying to improve things. If you would like to wrap log4net you can create your own logger by creating your own logging class that implements Mindscape.LightSpeed.Logging.ILogger. I hope that helps, John-Daniel Trask |
|