I know this sounds like a terrible idea, but it would solve a big performance issue for me. Does anyone have any experience or ideas on how to essentially bypass the transaction log when doing updates?
My application uses a SQL2000 database as a temporary processing area for a large batch...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.