Incepeti cu aceste documente Troubleshooting Performance Problems in SQL Server 2005, OLTP Blueprint - A Performance Profile of OLTP applications Cat despre 64 vs 32 performanta obtineti pe 64 doar daca pe 32 aveti probleme cu memoria. Altfel e posibil sa obtineti din contra o reducere a performantei din mai multe motive printre care: folosirea ...

SET XACT_ABORT ON   BEGIN TRANSACTION INSERT INTO Tabela1 .... IF @ERROR <> 0 GOTO Failure INSERT INTO Tabela2 ... IF @ERROR <> 0 GOTO Failure COMMIT RETURN Failure: ROLLBACK TRAN   In plus trebuie error handling in trigger.

Sau aici  http://sqlserver.ro/files/folders/tutorials/entry748.aspx

O introducere a acestui concept sub forma unui filmulet http://sqlserver.ro/files/folders/tutorials/entry748.aspx

In 2005 in cadrul unei intalniri ITBoard am realizat urmatorul tutorial: http://sqlserver.ro/files/folders/tutorials/entry748.aspx Daca vi se pare interesanta ideea vom continua insa numai daca exista feedback.

Pe aceeasi tema un tutorial realizat in 2005: http://sqlserver.ro/files/folders/tutorials/entry748.aspx

Iar SQL Server 2000 (inclusiv MSDE) nu va merge deloc http://www.microsoft.com/sql/prodinfo/previousversions/faq-sql_on_vista.mspx.

Correct! The Standard Edition needs 512 MB. On the specified hardware you can install the Express edition.

Correct! The right answer is: TestSrv.AdventureWorks.Sales.SalesOrderDetail

The answer is: Use the CONTAINS predicate.