August 5, 2011 at 3:52 am
The Gurus,
Which one is better - increasing the log by a value or by 10%?
Thanks.
Regards,
Sahoong.
August 5, 2011 at 4:04 am
It depends on what the activity is like.
August 5, 2011 at 4:06 am
Could you please, explain which is suited for which? Thanks.
August 5, 2011 at 4:13 am
Fixed value. The problem with % is that the growth increment increases as the file grows. It means that the time taken increases as well, and that can have impact on performance or even cause autogrow to timeout.
Fixed value, sensible size (not so small that it will grow often, not so large that the autogrow will timeout)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 5, 2011 at 4:40 am
Thanks Gail
August 5, 2011 at 4:57 am
I'm with Gail on this one. Fixed values are much better. You always know exactly how much will be added and you can anticipate the additional load that will place on the system. Knowing beats guessing every time.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 5, 2011 at 5:09 am
SELECT TOP 1000 [CASEID]
,[EVENTNO]
,[CYCLE]
,[EVENTDATE]
,[EVENTDUEDATE]
,[DATEREMIND]
,[DATEDUESAVED]
,[OCCURREDFLAG]
,[CREATEDBYACTION]
,[CREATEDBYCRITERIA]
,[ENTEREDDEADLINE]
,[PERIODTYPE]
,[DOCUMENTNO]
,[DOCSREQUIRED]
,[DOCSRECEIVED]
,[USEMESSAGE2FLAG]
,[GOVERNINGEVENTNO]
,[EVENTTEXT]
,[LONGFLAG]
,[EVENTLONGTEXT]
,[JOURNALNO]
,[IMPORTBATCHNO]
,[EVENTTEXT_TID]
,[rowguid]
,[EMPLOYEENO]
,[SENDMETHOD]
,[SENTDATE]
,[RECEIPTDATE]
,[RECEIPTREFERENCE]
,[DISPLAYORDER]
,[FROMCASEID]
,[DUEDATERESPNAMETYPE]
,[LOGUSERID]
,[LOGIDENTITYID]
,[LOGTRANSACTIONNO]
,[LOGDATETIMESTAMP]
,[LOGAPPLICATION]
,[LOGOFFICEID]
FROM [fbdlive].[dbo].[CASEEVENT]
I have the table above and I want to select all record for two different EVENTNO ( 1 and 100 for instance) but same CYCLE (3) for instance where the EVENTDUEDATE are different. Normally, on this record, if two or more different EVENTNO have the same CYCLE, their due date must be the same. How can I accomplish this?
Many thanks in advance
August 5, 2011 at 5:20 am
Please post new questions in a new thread. Don't hijack an unrelated thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply