|
|
|
Mr or Mrs. 500
      
Group: Administrators
Last Login: Wednesday, May 08, 2013 10:31 AM
Points: 511,
Visits: 945
|
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 1:12 AM
Points: 74,
Visits: 50
|
|
good article ... http://letslearnssis.blogspot.com/
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, May 20, 2013 9:54 AM
Points: 198,
Visits: 680
|
|
Where's the link to the next level?
I felt the same disappointment as getting to the end of an hour-long episode of a serial TV show: "Aw man, gotta wait till next week? I want more now!"
I'll be anticipating your next article. :)
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Yesterday @ 10:17 AM
Points: 133,
Visits: 437
|
|
If you do find that you have too many vlogs in your tlog how can you reduce the number of vlogs.What comes to mind is set the database to simple, shrink the tlog, set to full and then resize the tlog appropriately. Is there a more direct way and if not, does the way i outlined work?
I support a lot of systems that have databases for our software but we do not manage the databases. Many database start out with the default 1MB default log size with 10% auto growth. I would expect these sites would be susceptible to the problems described with large numbers of vlogs.
Jimmy
"I'm still learning the things i thought i knew!"
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 3:33 AM
Points: 122,
Visits: 99
|
|
Excellent Article Tony. Thank you.
|
|
|
|
|
Mr or Mrs. 500
      
Group: Administrators
Last Login: Wednesday, May 08, 2013 10:31 AM
Points: 511,
Visits: 945
|
|
Mike - it's great to hear you're looking forward to the rest of the articles. I hope you enjoy them! The first five levels can be found here. Bear in mind that if you get through these quickly, then you really will have a bit of a wait to read more .
imSQrLy - yes, that should work, though it might not be necessary to switch to SIMPLE, rather than just taking a log backup in FULL. Anyway, it's basically the way I'd do it, and is also the way Kimberly Tripp recommends: see Tip 8 in her "8 Steps to better Transaction Log throughput" article. Cheers, Tony.
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Tuesday, December 04, 2012 6:11 AM
Points: 14,
Visits: 196
|
|
Excellent Article! and very well explained. still I have very simple question.
I may be sounding asking a basic question but wanted to make some things clear here.
what happens when the last lets say n'th VLF(VLFn) is full with the logs and logs between VLF3 to VLFn are all active and full with logs. where will be the next LSN generated? will it be in VLF1 and VLF2 if they are inactive/reusable state? if yes what will be the LSN for those new logs? highest/lowest?
Thanks, Alpesh Pradhan
|
|
|
|
|
Mr or Mrs. 500
      
Group: Administrators
Last Login: Wednesday, May 08, 2013 10:31 AM
Points: 511,
Visits: 945
|
|
Hi Alpesh,
I should stress that I'm giving a simplified view of what actually happens, but yes the active log will "wrap around" so that that MaxLSN is now in VLF 1.
Tony.
|
|
|
|
|
SSCoach
         
Group: General Forum Members
Last Login: Monday, May 20, 2013 1:07 PM
Points: 18,733,
Visits: 12,332
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Wednesday, April 10, 2013 2:12 PM
Points: 129,
Visits: 439
|
|
imSQrLy (8/17/2011) If you do find that you have too many vlogs in your tlog how can you reduce the number of vlogs.What comes to mind is set the database to simple, shrink the tlog, set to full and then resize the tlog appropriately. Is there a more direct way and if not, does the way i outlined work?
I support a lot of systems that have databases for our software but we do not manage the databases. Many database start out with the default 1MB default log size with 10% auto growth. I would expect these sites would be susceptible to the problems described with large numbers of vlogs.
Don't set the db to simple or you'll break the log chain. If your db is full or bulk, take a tran backup and then shrink/resize the log.
|
|
|
|