November 25, 2009 at 7:41 am
Alvin Ramard (11/25/2009)
Roy Ernest (11/25/2009)
I sometimes feel that the thread rules us... We dont rule the thread anymore. It has evolved itself into a controlling beingTo the new folks in here, remember:
Resistance is futile. You WILL be assimilated!!!!
What? The Thread is a Norman?
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
November 25, 2009 at 7:48 am
Ok, I vote this as one of the more ... 'questionable' recommendations I've read here recently.
As your log file is very huge, and it is required to Truncate the log file for proper utilization of disk space, you need to stop the Mirroring activity, truncate the transaction log, change the database type to Simple (only if this is allowed in your business case), take a full backup and then reconfigure the database Mirroring.
Followed by
Reconfiguring the Mirroring database of 200 MB is small task and can be done in 30min - 1 hour time. This does not require the principal database down even (no downtime required). You should convience the business owner
Um. Yeah, well, ok....
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
November 25, 2009 at 7:51 am
GilaMonster (11/25/2009)
Ok, I vote this as one of the more ... 'questionable' recommendations I've read here recently.As your log file is very huge, and it is required to Truncate the log file for proper utilization of disk space, you need to stop the Mirroring activity, truncate the transaction log, change the database type to Simple (only if this is allowed in your business case), take a full backup and then reconfigure the database Mirroring.
Followed by
Reconfiguring the Mirroring database of 200 MB is small task and can be done in 30min - 1 hour time. This does not require the principal database down even (no downtime required). You should convience the business owner
Um. Yeah, well, ok....
I'll second that emotion Gail.
:w00t:
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 25, 2009 at 7:59 am
GilaMonster (11/25/2009)
Ok, I vote this as one of the more ... 'questionable' recommendations I've read here recently.As your log file is very huge, and it is required to Truncate the log file for proper utilization of disk space, you need to stop the Mirroring activity, truncate the transaction log, change the database type to Simple (only if this is allowed in your business case), take a full backup and then reconfigure the database Mirroring.
Followed by
Reconfiguring the Mirroring database of 200 MB is small task and can be done in 30min - 1 hour time. This does not require the principal database down even (no downtime required). You should convience the business owner
Um. Yeah, well, ok....
Yeah, my jaw hit my chest when I saw that one too.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
November 25, 2009 at 8:01 am
I'll give the poster of the first item one point for saying: "(only if this is allowed in your business case)"
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 25, 2009 at 8:05 am
GilaMonster (11/25/2009)
Ok, I vote this as one of the more ... 'questionable' recommendations I've read here recently.As your log file is very huge, and it is required to Truncate the log file for proper utilization of disk space, you need to stop the Mirroring activity, truncate the transaction log, change the database type to Simple (only if this is allowed in your business case), take a full backup and then reconfigure the database Mirroring.
Followed by
Reconfiguring the Mirroring database of 200 MB is small task and can be done in 30min - 1 hour time. This does not require the principal database down even (no downtime required). You should convience the business owner
Um. Yeah, well, ok....
Yeah, I was very happy to see you and Grant jump in on that thread. I made a an attempt at reason, but I was being overwhelmed and didn't have the energy to fight the hordes.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
November 25, 2009 at 8:05 am
GilaMonster (11/25/2009)
Ok, I vote this as one of the more ... 'questionable' recommendations I've read here recently.As your log file is very huge, and it is required to Truncate the log file for proper utilization of disk space, you need to stop the Mirroring activity, truncate the transaction log, change the database type to Simple (only if this is allowed in your business case), take a full backup and then reconfigure the database Mirroring.
Followed by
Reconfiguring the Mirroring database of 200 MB is small task and can be done in 30min - 1 hour time. This does not require the principal database down even (no downtime required). You should convience the business owner
Um. Yeah, well, ok....
um bdm bdm bdm
Interesting recommendation. Maybe the OP will try it, then will need somebody to help fix it:-)
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 25, 2009 at 8:08 am
Alvin Ramard (11/25/2009)
I'll give the poster of the first item one point for saying: "(only if this is allowed in your business case)"
No points from me for that. That comment looks like it only applies to the 'switch to simple', by that point the mirroring's dropped and the log truncated. Switching to simple by that stage can't do any more damage than has already been done.
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
November 25, 2009 at 8:11 am
GilaMonster (11/25/2009)
Alvin Ramard (11/25/2009)
I'll give the poster of the first item one point for saying: "(only if this is allowed in your business case)"No points from me for that. That comment looks like it only applies to the 'switch to simple', by that point the mirroring's dropped and the log truncated. Switching to simple by that stage can't do any more damage than has already been done.
I agree that it applies to "switch to simple". The one point is only because this implies a "check before proceeding".
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 25, 2009 at 8:11 am
Maybe y'all should give awards for worst suggestions. I'm sure the competition is tough.
__________________________________________________
Against stupidity the gods themselves contend in vain. -- Friedrich Schiller
Stop, children, what's that sound? Everybody look what's going down. -- Stephen Stills
November 25, 2009 at 8:13 am
Bob Hovious 24601 (11/25/2009)
Maybe y'all should give awards for worst suggestions. I'm sure the competition is tough.
........ and the winner is ... (drum roll) ... Oh, it looks like we have a 73 way tie for first place.
:w00t:
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
November 25, 2009 at 8:20 am
Alvin Ramard (11/25/2009)
Bob Hovious 24601 (11/25/2009)
Maybe y'all should give awards for worst suggestions. I'm sure the competition is tough......... and the winner is ... (drum roll) ... Oh, it looks like we have a 73 way tie for first place.
:w00t:
Sounds about right.
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
November 25, 2009 at 8:23 am
Alvin Ramard (11/25/2009)
Bob Hovious 24601 (11/25/2009)
Maybe y'all should give awards for worst suggestions. I'm sure the competition is tough......... and the winner is ... (drum roll) ... Oh, it looks like we have a 73 way tie for first place.
:w00t:
Hey.... I did not give any suggestions... So it should be a 72 way tie for first place... 🙂
-Roy
November 25, 2009 at 8:24 am
Is that a 73-way tie for first place on a daily basis?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
November 25, 2009 at 8:26 am
CirquedeSQLeil (11/25/2009)
Is that a 73-way tie for first place on a daily basis?
I can't say Jason. I only have ten fingers so these bigs numbers can be a problem every now and then.
😉
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
Viewing 15 posts - 9,511 through 9,525 (of 66,000 total)
You must be logged in to reply to this topic. Login to reply