thanks

As you only have 4GB of memory and AWE is to enable memory usage above 4GB, AWE is not applicable here.

Unless you see messages in your SQL error log to...

for the benefit of others what was your solution?

Unless your databases are almost exclusively read only it is definitely a good idea to separate data from log.

At 1.5Gb SQL is taking about the max for the buffer pool it is able to in your scenario.

Try setting the /3Gb switch in the boot.ini to allow SQL another...

have you configured it via reporting services configuration manager?

http://msdn.microsoft.com/en-us/library/ms157412.aspx

MyDoggieJessie (3/1/2012)

---

This is also typical behavior when the query/statement you killed spans across a "linked server". If your query does perform TSQL on a linked server, you need to...

explains the deja vu.

now we need a question on which role has the...

should we be encouraging the use of 'select...

I guess so we knew it was a case insensitive collation

Be aware the uniqueidentiier values are random and therefore I would have thought not a good value to partition by.

If you have to use this use it in conjunction with...

you should see the login failure reported in the SQL errorlog with some information as to the cause, including an 'error state'.

Hers a list of the common reasons and their...

not uninterested - perhaps this is a...

truncateonly option is ignored with a log shrink.

truncate_only is no longer a log backup option in SQL2008

You can shrink your log and database files if you really need to...

you are confusing notruncate in log backups with notruncate in shrinking.