Richard,

first of all Taskmanager is not very reliable when showing SQL Server memory. Use Performance Monitor instead.

Second SQL Server wil not reserve RAM at startup unless you defined a minimum...

Oops,

sorry Lowell my comment was about Jeff's script. I must admit I was in a hurry yesterday...

Hi Jeff,

what I was hoping to find was a script which gives the the max actual value for the whole row. The idea was to find rows which could cause...

Mj,

since you write that the server uses the wrong plans, my first hinch would be that the statistics have not been updated after the upgrade. All stats from SQL 2000...

Hello Lowell and Jeff,

thank you both for your efforts.

Even though it's still not exactly what I had in mind, I think I can work with your scripts.

Markus

Todd,

just out of interest. In my tests my query did not return NULL. Which test data where you using? You sure you run it on SQL 2005?

Markus

Lowell,

thanks for your response, but thats not what I'm looking for. I already have a script which calculates the defined rowlength. What I now try to find out is the...

Another case where you can use the logical filename is BACKUP/RESTORE of a databasefile.

Markus

As you already found out, the execution plan is exactly the same. The reason for this is that the Query Optimizer realises that both queries request the same data and...

Hi Chris,

generally I prefer to use UNC  names when accessing network resources. I know that in SQL 2000 mapped drives often caused problems, not sure if 2005 reacts the same....

Try this:

SELECT t1.*

FROM   table1 t1

       JOIN (SELECT id

             FROM   table1

             WHERE  yn = 'Y'

             INTERSECT

             SELECT id

             FROM   table1

             WHERE  yn = 'N') t2

         ON t1.id = t2.id

P.s. it...

There are basically two DMV's you can use.

sys.dm_exec_requests gives you real time information

SELECT

st.text, r.*

FROM

sys.dm_exec_requests r

CROSS APPLY

sys.dm_exec_sql_text(sql_handle) AS st

WHERE

r.session_id = 112

sys.dm_exec_query_stats gives you historical information about all...

You need to change the database state by using

ALTER DATABASE <database_name> SET PARTNER OFF

see also http://technet.microsoft.com/en-us/library/ms189112.aspx

Markus

Molly,

ALTER INDEX is a new statement in SQL 2005. Since you posted this in the 2000 group I assume that you're using SQL 2000 and that explains the error. Anyway...

I don't think there's a stored procedurereadily available is SQL Server but you can try this script http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=520

Another option I use a lot is the SQLDumpSec utility. It's simple...