Hi,

if you have the Autogrow set to 10%, then it seems to me that it grew just as much as it is allowed to in one jump - original size...

Hello,

I may be wrong, but I think this behavior is due to Parallelism - more complex queries on large tables will be split into several processes running at the same...

Hi,

just one more thing in addition to what has already been said:

Do you have any processes in any of the databases that could cause extensive locks or use large proportion...

We have currently 7 user databases on the server, one of them has around 90GB, the other are small (200-600 MB), have limited number of users (up to 10) and...

andoi,

your description almost matches what we were experiencing - I know that situation very well, our disks were at 100% most of the time, too. I agree with your proposal...

quote:

---

Reminder: There are such things as "her" resume.

---

You are absolutely right, Dale. But please,...

I prefer to write about history in the order it was happening, not backwards as usual in CV, so:

studies - Hydrobiology and Ecology at university

jobs -

- TEMPUS/PHARE project coordinating assistant...

jscii, it looks like it should be enough, but there are operations which may require more space to be completed... I remember we got the same error a few times,...

Hmm... I'm afraid these queries won't accomplish the goal (at least as I understand it), which is to select top 6 departments from EACH store - not the top 6...

I don't feel "strong" enough to give you advice about what's causing the problem and why, but I can at least answer one of the questions: Size of tempdb varies...

I know I'm not answering the question, but it isn't entirely off topic.. I just wanted to remark that we had substantial problems with performance while using RAID 5 (almost...

Nice thing... may I suggest that it would be even better if you modify it so that it works automatically with words of any length? As it is, one has...

The above answer is what you need, I guess...

I just wanted to comment on the error you were receiving: Reason is that the order is incorrect, distinct should come first,...

Well, I'm not sure I understand the problem correctly, but one of the main questions seems to be whether the last row (with MAX(id)) always contains the highest entrydate -...

What ronc wrote about the optimizer explains my results in certain complicated queries where big tables (several millions of records in each) are joined: SELECT TOP 500 uses index and...