Viewing 15 posts - 46 through 60 (of 350 total)
Here we are (sorry, if this is wrong way to post script):
******************************************************************
[font="Arial"]USE [DBA]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- ============================================================
--rebuild index using dbo.index_rebuild_log ahead prepared data
-- ============================================================
CREATE PROCEDURE [dbo].[usp_IndexRebuild]
AS
BEGIN
SET NOCOUNT ON;
declare @start...
May 26, 2013 at 11:06 am
1) 2005- Sql Server 2005 Practical Troubleshooting- Ken Henderson and Co
2) 2008- Troubleshooting SQL Server - A Guide for the Accidental DBA- Kehayias, Jonathan
Enjoy reading 🙂
May 26, 2013 at 10:47 am
Just did this yesterday night, i.e. break/restore Mirror:
1. restore Full backup with NoRecovery
2. restore all sequential TrLog backups with NoRecovery
3. setup partners on Principal and Mirror to point to each...
April 11, 2013 at 4:25 pm
Mirror Monitor is your first friend- it provides info on: how long it can take to sync, latest moved transaction, etc. A lot of helpful info
March 13, 2013 at 6:27 pm
Just to confirm that changing backup retention period from 1 day to 23 hours solved this mystery (from time to time failed old backup cleaning) for me too
January 29, 2013 at 8:07 pm
Thanks guys for all your answers-
just to summarize- for index maintenance we need to take into account both logical fragmentation and page density. Still have couple questions left: 1)...
January 6, 2013 at 7:24 am
It makes sense to consider internal fragmentation while making decision to rebuild indexes- why in this case majority scripts/advices (including mentioned BOL sample) do not care about it (only external...
January 5, 2013 at 9:32 pm
To resume- restored DB is always identical backed up one (like mirror copy). Thanks a lot, Gail for your time and detailed explanation. Yuri
October 16, 2012 at 8:34 am
Make sense- thanks. If you do not mind 1 more question- regarding TrLog- same story or not? I mean original DB has 90% free log (let say after huge index...
October 15, 2012 at 3:38 pm
Sorry Gail but IMO it does not sound logical- if during backup only used (with data) pages are written to backup file then restored DB should have only such pages...
October 15, 2012 at 2:28 pm
Bhuvnesh (10/15/2012)
Yuri55 (10/14/2012)
What means "used pages"? Can you please clarify. Thanksused means the pages which contain data .
refer this link http://msdn.microsoft.com/en-us/library/ms175477(v=sql.90).aspx
Make sense, thanks
What does not make sense...
October 15, 2012 at 9:56 am
What means "used pages"? Can you please clarify. Thanks
October 14, 2012 at 4:05 pm
Kevin,
How big is your DB? I had same issue trying to backup TB DB. Eventually did local backup and then copied file to network storage
June 7, 2012 at 9:20 pm
As per this book recommendation this value (AvailableMbytes) "it remains above 150–300 MB". Probably that mean in my case (around 100 MB) we should decrease a bit Max memory value...
March 28, 2012 at 9:38 am
"Monitor, if you see memory allocations keep dropping very"
Can you advice- what to monitor? I know, know- a lot of info, but honestly very often it's not clear and confusing....
March 28, 2012 at 9:00 am
Viewing 15 posts - 46 through 60 (of 350 total)