Not too bad at all, it definately covered the normal user requirements

Unfortunately our system is growing at geometiric rates (was 10GB a week...

I thought that it was a decent article, and one very close to my heart as  our DB is currently 1.6TB and growing by 15-30 GB each and every week.

To be honest I really don't know but I would wonder what difference it would make.

Or do you mean something like identity columns rather than extents?

It's not enough having enterprise edition, you also need to fullfil the criteria that is described in books online.

just open it up and type indexed view, you should then see...

Bad Data, down boy

We had a similar problem a couple of months ago when our feed was accidentally changed from 100 to 10, it was annoying because it took us around 4 hours...

I don't know if it's still the case but a similar thing used to happen if you ran the job yourself as opposed to letting it run as a scheduled...

You should also try taking a look at the queries that run most often, even if they are already quite fast.

Tuning the long running queries is fine, but you can...

Actually all data used in SQL comes from memory, the only sticking point is whether it is already in memory or whether it needs to be brought into memory from...

A great article, I was really looking forward to intellisense being available in sql 2005 until they decided to drop it.

I can see this being a useful in our environment...

That depends on what you're using, I assume you script the DB objects in SQL and the encrypted ones don't get transferred because they can't be scripted?

You can either use...

The last time I had a problem like this I ended up rebooting the server at which time it started working properly again.  I can't guarentee that it will for...

No Problem Jan,

You could also take a look at software from companies like Quest, i beleive they have this sort of thing available (at a cost), i've not used them...

Does it need to be 100% synchronous (ie 2 phase commit?)

Unless you can work around the problems with replication (what are they by the way?) I think you're stuck with...

It sounds like a permissions problem, can server 'B' access server 'A's shares?