actually this was a trick for who don't how 64bit env works.

the first 2 options are valid in 32bit env, and I bet that a lot of people will choice...

yes, the question would be better if talked about: what do you need to do for sql server recognize more than 2GB of memory in an 64bit environment?

to allocate the...

This QotD and Andreas'reply were a great tip.

Hi everyone,

My SQL Server goals to 2010 are:

1) get MCITP SQL Server 2008 DBA and DEV (yeaahhh, both...lol)

2) write SQL Server articles for an international website, SSC here we go...lol

3)...

It's true, is very important to have a professional development plan.

I like to read Microsoft Resource Kit books, because they have a well defined sequence to study. This kind of...

In big companies the database security is better (not perfect), in medium or small companies I’ve seen basic security failures.

So, this sounds like a good idea, but maybe an utopia.

Hi,

Take a look at this article:

http://blogs.msdn.com/psssql/archive/2009/03/03/how-it-works-almost-everything-you-wanted-to-know-about-the-sql-server-2005-2008-performance-counter-collection-components.aspx

Hi guys,

It's very important to test the sysadmin connections before remove the BUILTIN\Administrator group, but don't forget that since MSSQL 2005, we have an workaround if the SA password was...

One of my favourites:

http://www.amazon.com/Pro-Server-2005-High-Availability/dp/159059780X/ref=sr_1_1?ie=UTF8&s=books&qid=1241394215&sr=1-1

If the Distributor account has SYSADMIN permissions, will be work.

A database set to RESTRICTED MODE allow access to all connections with DBOWNER (or higher).

Sysadmin is a permission higher than dbowner.

So,...

No, it's not possible.

But if you didn't grant Windows account access to MSSQL, you'll have only MSSQL logins working on the instance.

Ensure that BUILTIN\Administrator was removed too.

In Windows Server isn't possible as Unix Server (not MSSQL off course).

You need to uninstall and install again.

Make a database backup if needed.

What about this line?

exec sp_trace_setfilter @TraceID, 11, 0, 1, N''

A column NOT LIKE '' using an AND operator will return more records.

Hi...

yeap...archive log for further analysis (if necessary).