All the sites I'm seeing show that the conditional variable, if characters, needs to be in quotes.

=iif(Fields!COSTYPE.Value = "M","Available","Reconciled")

looks like the right syntax.

(not an ssrs expert)

perhaps it's a data type...

I did some more testing, focusing on reorganize since it is the culprit of the log growth. I ran the same test sequence four times for different fill factors. Here...

Thanks for the question.

I was about to encite a forum riot with "it depends how big the log is and you didn't say!!!! bad question! bad poster! trick question!...

Christoph,

Yes, each round I would truncate the log before introducing fragmentation. The rebuild was happening offline (default).

Alright, it didn't go as expected. I set sort_in_tempdb = on and didn't get the results i expected. Looking over the logs, the index was reorganized and not rebuilt. This...

Yep. It's happening Saturday night and there's no...

Thanks Chris,

I was thinking more about it last night (dreaming of sql server? i need a break) and thought of an additional caveat to using sort_in_tempdb. When I rebuild indexes,...

Satish,

I ran into a very similar issue recently. When my indexes would rebuild on the weekend, my log would inflate 300%. It will stay that way until the next log...

David Bird (1/5/2011)

---

I could see using this script on a SQL express installation without SQL Agent installed. Windows Scheduled Taks would be used for scheduling it.

I am not sure...

Koen (da-zero) (1/5/2011)

---

The original question didn't say anything about starting SQL Server Agent.

However, an answer from MS Support in the thread you linked to (the link doesn't work by the...

Sounds like it's a problem with the windows/user account you're using to start the SQL Agent service.

Are you using a user account or a local system account to start the...

TheSQLGuru (1/4/2011)

---

1) why in the world are you concerned about a 279MEGABYTE transaction log?? If your disk space is that tight you have some very serious issues to deal...

GilaMonster (1/4/2011)

---

Not entirely true.

Checkpoint writes all dirty data page to disk and then, in simple recovery only,...

Checkpoints flush buffer cache to disk. Nothing to do with truncating a log.

http://msdn.microsoft.com/en-us/library/ms188748(v=sql.90).aspx

A full backup doesn't truncate the log, that's why the t-log doesn't shrink. Only a transaction log backup will truncate the log and allow shrinkage.

A full only backs up data...