A good backup strategy designed according to the downtime and data loss requirements of the application.

The estimated row count on your actual physical table is wrong. SQL thinks that the physical table contain only 1000 rows and hence that a scan of the physical table...

Sure, it's fine for secondary reporting systems. It's just bad for hot failover...

Post the execution plans?

btw, as an aside, in case...

Replication is not a high availability technique. While it can create a copy of a database, it's a pain to switch apps over, it may not be a complete copy...

Yup. Poorly written queries, inadequate indexing. Main causes of any perf problem.

Somedays I think they're finding me. If my divining rods worked, I'd use them to avoid some...

subs99 (2/5/2010)

---

Or does SQL mindlessly try to do a Log file backup right during a Full backup? That would really mess things up, wouldn't it? What if it did a...

There's no object called 'YourQues' anywhere in...

suresh.maddali (2/5/2010)

---

Attach the data base --> Right click on Data base and choose attach. before this we need to complete following

1. Go to c:\Program files\Microsof Sqlserver\MSSQL.1\Data...

zhayatali (2/5/2010)

---

then user told me we are facing such problem then i taken full database backup at 12:51.in this satuation can we go back database state before 12:41 or not...

The backup that you took at 12:51 cannot be used to restore to 12:30. There's no time machine in SQL.

You need to take the latest full backup from before 12:30,...

What more are you looking for?

http://sqlinthewild.co.za/index.php/2007/11/15/execution-plan-operations-scans-and-seeks/

http://sqlinthewild.co.za/index.php/2008/04/23/execution-plans-important-properties/

With the 3 indexes that you have defined there, the only queries that will perform optimally there will be the ones that filter on a single column. When using predicates...