Viewing 15 posts - 631 through 645 (of 687 total)
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...
January 13, 2011 at 9:59 am
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...
January 12, 2011 at 8:56 am
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!...
January 12, 2011 at 5:34 am
Christoph,
Yes, each round I would truncate the log before introducing fragmentation. The rebuild was happening offline (default).
January 11, 2011 at 10:03 am
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...
January 11, 2011 at 7:11 am
TheSQLGuru (1/7/2011)
Good luck with the testing. Don't forget to size tempdb appropriately and not wait for autogrowths to size it for you.
Yep. It's happening Saturday night and there's no...
January 7, 2011 at 8:00 am
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,...
January 6, 2011 at 8:32 am
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...
January 6, 2011 at 8:26 am
David Bird (1/5/2011)
I am not sure...
January 6, 2011 at 6:35 am
Koen (da-zero) (1/5/2011)
However, an answer from MS Support in the thread you linked to (the link doesn't work by the...
January 5, 2011 at 6:27 am
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...
January 5, 2011 at 5:52 am
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...
January 4, 2011 at 8:31 pm
GilaMonster (1/4/2011)
calvo (1/4/2011)
Checkpoints flush buffer cache to disk. Nothing to do with truncating a log.
Not entirely true.
Checkpoint writes all dirty data page to disk and then, in simple recovery only,...
January 4, 2011 at 2:54 pm
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
January 4, 2011 at 1:40 pm
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...
January 4, 2011 at 10:21 am
Viewing 15 posts - 631 through 645 (of 687 total)