Hi §unshine,

It works only in SQL Server 2005.

Regards.

Thanks a lot MANU-J

Hi,

The best explanation I found, Microsoft used the 'AWE' param for other thing (to use locked pages in memory).

http://blogs.msdn.com/slavao/archive/2005/11/15/493019.aspx

Regards

Hi,

You can use BCP instead. Just take time to build yours scipts.

regards

Hi,

The user need to be member of db_ddladmin at least.

http://msdn.microsoft.com/en-us/library/aa260621(SQL.80).aspx

Regards

Thanks Perry.

Thanks Steve,

I have just another concern, if we add new instances on each node, so the memory on each node will be shared between instances I think so.

Ahmed

Hi DBA,

I customized the script provided in the following link, it works very well for huges databases http://blogs.digineer.com/blogs/larar/archive/2006/08/16/smart-index-defrag-reindex-for-a-consolidated-sql-server-2005-environment.aspx

Regards,

Ahmed

Hi,

Get a free book from http://www.devx.com/RedGateVS/Door/37329

http://www.sql-server-performance.com/tips/sql_server_performance_monitor_coutners_p1.aspx

http://www.sql-server-performance.com/tips/performance_monitor_general_p1.aspx

http://www.windowsitlibrary.com/Content/77/15/1.html

http://www.mssqltips.com/tip.asp?tip=1265

http://whitepapers.zdnet.com/abstract.aspx?docid=337037

http://sql-server-performance.com/articles/per/System_Monitor_Hardware_Bottlenecks%20_p1.aspx

http://sql-server-performance.com/articles/per/sys_dm_os_performance_counters_p1.aspx

regards,

Ahmed

As I said in my previous post check also the link

http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/Q_22009002.html

just take time to do it.

Check the link http://msdn.microsoft.com/en-us/library/ms365338.aspx

hi,

Try to use openrowset instead

http://technet.microsoft.com/en-us/library/ms190312.aspx

http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SQL-Server-2005/Q_23146199.html

Like Mani said, you need to audit connections to SQL Server then check the error_log.

http://www.microsoft.com/sql/prodinfo/previousversions/securingsqlserver.mspx

Just For info

Anyway, to summarise; Windows 2003 R2 Standard Server x32 has a maximum of 4GB of RAM, Windows 2003 R2 Standard Server x64 has a maxium of 32GB of...

Hi,

Just use sp_who2.

If you need more info just cutomize sp_who2 for your needs

Regards