171 reputation
29
bio website hinternets.blogspot.com
location Middle Earth
age 36
visits member for 3 years, 2 months
seen Feb 19 at 23:40

A rolling stone gathers no moss, so they say.


Feb
8
comment SQL Calculated Field in both SELECT and GROUP BY clause
Using cross apply in this case is a bit of a stretch, and it would very likely harm performance by introducing a needless self-join.
Feb
7
revised SQL Calculated Field in both SELECT and GROUP BY clause
added 29 characters in body
Feb
7
comment SQL Calculated Field in both SELECT and GROUP BY clause
Unfortunately, oftentimes your only way out of specifying the expression twice is to use one of the above methods: a CTE, view or a nested query.
Feb
7
answered SQL Calculated Field in both SELECT and GROUP BY clause
Oct
31
awarded  Notable Question
Jul
23
awarded  Notable Question
Dec
21
awarded  Popular Question
Nov
3
awarded  Popular Question
Dec
31
comment Keep transaction log size under control during batch processing
It's occurring on a development server with no automated backups or any other task. For all intents and purposes, I have exclusive access to it.
Dec
29
comment Keep transaction log size under control during batch processing
I don't think running in restricted access is an option, since the main requirement is that the system needs to be live during this maintenance job, and that includes querying and insertion of more data.
Dec
28
awarded  Scholar
Dec
28
awarded  Commentator
Dec
13
comment Keep transaction log size under control during batch processing
I have updated my question to be more clear about what I'm asking. It's not so much about minimising the data:logging ratio, but just ensuring that existing log space is reused.
Dec
13
revised Keep transaction log size under control during batch processing
Clarified question.
Dec
13
comment Keep transaction log size under control during batch processing
@SqlACID, yes. In development it's pretty much a default SQL 2008 R2 database. The recovery model is the only thing that has changed (from FULL to SIMPLE) as far as I can see.
Dec
13
awarded  Student
Dec
12
comment Keep transaction log size under control during batch processing
Look, this question is about how to prevent the runaway log scenario in the first place, not how to deal with it afterwards. Please stay on topic.
Dec
12
comment Keep transaction log size under control during batch processing
I have been able to confirm that no full backup was run on this database overnight, so that cannot be the cause either.
Dec
12
comment Keep transaction log size under control during batch processing
Hmm, I hadn't considered the impact of a full backup until now.
Dec
12
comment Keep transaction log size under control during batch processing
@BalamBalam: Both cases are equally unacceptable for my situation. The script needs to not cause runaway log files.