New_to_being_DBA (7/31/2008)

---

HI All, We're trying to configure a new server and I need some input on the best way to do it.

We have a 64 bit, 40 G of...

Hi,

Whenever we apply a patch to the OS or SQL we do full testing of all applications. This can be painful if it's not automated.

Perry Whittle (7/31/2008)

---

the 2 HBA's should be multi homed so that in the case of an HBA failure you dont lose any of your data drives.

In the options you are...

To add to this:

Like he said, growing the data file hurts performance since the database must be totally locked to grow. It may also give you fragmentation...

You could deposit the trace file into a table periodically and then schedule a job to run t-sql procedure which searches for the sp_configure query. Use the sp_notify_operator(maybe not...

In SSMS right click your DB and select Reports->Standart Reports->Disk Usage by Top Table.

This should get you started.

We're using another product, not litespeed.

64 bit sql 2005

We are using HP EVAs

Turned out that we also had a problem with a virtual sql server - the backup software conflicted with sql and caused it...

We've opted for the server guys to monitor the memory usage of all processes and set up an alert for when the error comes up again. I reviewed the...

We have the memory capped - with 2GB shy of the total server memory. This is a dedicated server with just SQL on it. I don't believe it...

I looked in the cluster admin at the network interfaces listed and then...

Hi Matt - I appreciate your help.

I have redacted servernames with NODE1, NODE2, CLUSTERNAME

Here are some logs.

First, it looks like we got this error at 7:04AM, 6:05PM, 6:19PM,...

The virtual server turned out to be an issue with a disaster recovery backup snapshot happening and sql trying to write at the same time.

Vendor says he highly...

Colin,

Yes we did shut down the dev servers that were being affected by the install. The productions servers should have taken an alternate route through the mds which wasn't...

Supposedly, the san software only affects disk areas that have been 'imported' into it. Production systems were not imported. Now they are being affected. We had one...