correct, the only things necessary is the AWE option and the lock pages in memory permission for your SQL account.

I know for a fact that it is necessary to use AWE - I've tried it without doing so.

make sure the execution account is setup properly. open the login and ensure that the login has access to it's default database.

yes, you can use 64GB, but you need to enable AWE for 32 bit.

well, it's a real sticky one when dealing with a problem like this where it could be SQL or exchange. it's hard to say where to concentrate your efforts. Personally,...

Well, I'm not sure on that one. Like I said, I have experienced that issue outside of SQL, and I'm not really sure what fixed it. I assumed the exchange...

you could write a stored procedure that does you select and give them execute on that stored procedure. That way they can do their select without having permissions on the...

I have had this happen outside of SQL. On of my colleagues would send me an email and it would come through twice. We verified that he only sent it...

Indeed, however, they all know not to restore this database and hopefully this will remind them. I'm also adding text to the alter database trigger to remind us that we...

I'm going to use a SQL job to do that loop and keep a connection open and an alter database trigger that will prevent them from putting the database in...

Luckily this is a test server, but it does cause others quite a bit of work if it is overwritten.

if you use sp_execute, the plan will be more likely to be reused on multiple executions. Otherwise, if you don't want to use synamic SQL, you could have conditional statements...

1 - yes, they are still faster than in line SQL. They are precompiled and SQL makes some assumptions on what it thinks will likely be passed to it.

2- that...

this doen't always work, but we have had some sucess with it. try creating your odbc source from this location:

c:\windows\syswow64\odbcad32.exe

A Les Paul silverburst! what a sweet guitar that is!