If you had ten gallons of water and a five gallon bucket, would you try to pour all ten gallons into that five gallon bucket? No? Why not? Probably because you can clearly see that the volume mismatch will cause a problem of sorts. Unless, of course, you really just want five gallons and you do not care if anything gets spilled.
So, if you would not pour ten gallons into a five gallon container, why would you continue to try that data load? You know…the one that keeps generating that ‘trx log full’ error message? I suppose I could understand if you were trying different ways to get it done correctly, but to make seven attempts, hoping for a different outcome the last six times, is very, very close to the definition of insanity.
You may want to check your code. Or check yourself into a clinic. Or understand what your code is trying to do; how big the transactions will be, how big the file is currently, what it means to have a checkpoint, etc. I’m just sayin’, that’s all.
The ETL guys I’ve worked with tend to say that it’s the DBA’s fault for not emptying the bucket faster. They tell me to quit holding up the process. (sigh)
sounds like a real bunch of Jokers…
even if i emptied it as fast as possible, they would still write a query to cause the system to bork.
You never stop on an odd number of attempts. That’s your problem right there. Attempt #8 would’ve solved the issue without a doubt. *whistles innocently*
The definition of insanity is doing the same thing over and over expecting a different result.