Viewing 15 posts - 1 through 15 (of 232 total)
Hi §unshine,
It works only in SQL Server 2005.
Regards.
August 13, 2010 at 7:00 am
Thanks a lot MANU-J
March 22, 2010 at 5:10 am
Hi,
The best explanation I found, Microsoft used the 'AWE' param for other thing (to use locked pages in memory).
Regards
June 9, 2009 at 10:49 am
Hi,
You can use BCP instead. Just take time to build yours scipts.
regards
June 4, 2009 at 4:33 am
Hi,
The user need to be member of db_ddladmin at least.
Regards
December 4, 2008 at 1:00 am
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
September 17, 2008 at 8:13 am
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
August 13, 2008 at 1:14 pm
Hi,
Get a free book from http://www.devx.com/RedGateVS/Door/37329
regards,
Ahmed
June 30, 2008 at 8:50 am
As I said in my previous post check also the link
just take time to do it.
June 26, 2008 at 12:13 pm
hi,
Try to use openrowset instead
June 26, 2008 at 8:06 am
Like Mani said, you need to audit connections to SQL Server then check the error_log.
June 26, 2008 at 7:53 am
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...
June 26, 2008 at 7:41 am
Hi,
Just use sp_who2.
If you need more info just cutomize sp_who2 for your needs
Regards
June 26, 2008 at 7:29 am
Viewing 15 posts - 1 through 15 (of 232 total)