Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Foreign Keys,Deadlocks, Partioning,OLTP ......what is the best setup? Expand / Collapse
Author
Message
Posted Tuesday, January 29, 2013 8:17 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, April 14, 2014 9:42 AM
Points: 104, Visits: 359
We are using AlwaysOn to a DR site so we do have High Availability

The 2 hour restore is if we lose both it has to be available within 2 hours

Overkill?
Post #1413073
Posted Tuesday, January 29, 2013 8:23 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:05 AM
Points: 14,802, Visits: 27,276
DominantDBA (1/29/2013)
We are using AlwaysOn to a DR site so we do have High Availability

The 2 hour restore is if we lose both it has to be available within 2 hours

Overkill?


Nah, business requirements. Whatever they are is what they are as long as they're physically possible and within the budget being provided. But, it does sound like you might be solving one problem and introducing a second with partitioning. I'd recommend some VERY thorough testing around these changes, especially dropping the FKs for triggers. I think that one is crazy, especially if you're already experiencing performance problems.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1413075
Posted Tuesday, January 29, 2013 9:51 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 11:52 AM
Points: 41,530, Visits: 34,446
DominantDBA (1/29/2013)
We are using AlwaysOn to a DR site so we do have High Availability

The 2 hour restore is if we lose both it has to be available within 2 hours

Overkill?


No, but I'd probably consider something like log shipping to a tertiary (maybe an hour behind primary) for the 'must be up in 2 hours', rather than jumping through hoops with tweaking backups. But then, last system I worked on with requirements like that was over 1 TB and restoring backups was a 4-6 hour process.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1413161
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse