Darn - it was worth a shot, too bad it didn't help. The only other thing I can think of would be to see if you can upgrade the...

Like I said - try upgrading the client tools to SP3 and see if that helps. That would be 9.00.4035.00...

Haven't seen it myself, but I am wondering how large the mdf file is? Could it be an issue where the data file is too large for Express?

What version of the client tools are you installing? Have you tried upgrading the client tools to SP3 to see if that helps?

TheSQLGuru (8/20/2009)Several incorrect statements there. It can occur on a SQL Server only box that the OS asks for memory back. Also SQL Server does give memory...

Yes, you can more or less ignore the index fragmentation for those tables. What I normally do is schedule a weekly index rebuild for smaller systems and just select...

Yeah - that doesn't work in 2005. It might work in 2008 - but I wouldn't count on it.

oraculum (8/19/2009)

---

Still think i'm being misunderstood, the memory allocated is 24GB this is fine and as expected as its the Max Server Memory...

The problem is that 75% of that 'allocated'...

Thank you for the feedback - I am sure it will help someone down the road.

SQL Server will only release memory back to the OS when the OS needs that memory. On dedicated SQL Server machines - that will never occur. If you...

And you expected something different? Isn't there a...

I have not done so myself, but I believe Litespeed will integrate with TSM. AFAIK, SQL Server native backups do not integrate natively with TSM.

What was the problem? It would be helpful for anyone else who has a similar issue to know what you had to do to fix this problem.

thanks

If I was building this system, I would not be building it on SQL Server 2005. I would be building this on SQL Server 2008 and implementing filestream access...

SQL Server will allocate memory up to the max memory setting and keep that memory. It does not release the memory. What you are seeing is normal behavior.

On...