Asadar:http://www.brentozar.com/archive/2010/03/plagiarism-inspiration-and-john-dunleavy/http://itknowledgeexchange.techtarget.com/sql-server/plagiarism-inspiration-and-john-dunleavy-madder-and-more-pissed-off/Si mai jos preturile pe care le practica plagiatorul:http://sqltechconsulting.com/rates/

http://dbmanagement-blog.com/sql-server-dba-training-videos/

http://www.sqlpass.org/LearningCenter/24Hours.aspx

Macar pentru cel mai recent statement per sesiune poti incerca SELECT conn.most_recent_session_id, conn.client_net_address, qry.TEXT FROM sys.[dm_exec_connections] conn CROSS APPLY sys.[dm_exec_sql_text](conn.[most_recent_sql_handle]) AS qry Sursa: http://www.mssqltips.com/tip.asp?tip=1799

Te gandesti si la performanta (logul e secvential), si la spatiu si la redundanta (mirror sau RAID 10)

Daca tot cumparati discuri - e bine ca logul sa stea pe un disc dedicat.

Presupun ca lucrezi pe recovery model full. Vezi http://sqlserver.ro/forums/thread/8306.aspx http://www.sqlservercentral.com/Forums/Topic925739-391-1.aspx#bm925746 Daca stapanii tai accepta pierderea de date (depinde si de cat accepta), gandeste-te sa usurezi administrarea trecand pe ''simplu''. Daca ramai pe full, vezi ca beckup-urile de log ...

Vezi si http://sqlserver.ro/forums/8317/ShowThread.aspx#8317

Iata link-ul promis ieri http://www.sqlservercentral.com/Forums/Topic912575-361-1.aspx#bm931717 Pe de alta parte se pare ca nu esti singurul care are problema asta http://sqlserver.ro/forums/thread/8316.aspx

Pai cine-o fi facut aplicatia aia? :)