You could install developer edition rather than standard. It's cheap ($50) and will full enterprise features, just not for use in a production environment. It installs on Vista and XP...

Not that I know of, but on SQL 2005 (which I assume you're using because of teh forum this is posted in), you can enforce password policy which includes a...

Express does not include SQL agent.

Warren Peace (5/29/2008)

---

So, I guess one can say if the TX files ARE being backed up truncating the TX file on a weekly basis should be OK? I say this...

Matt Miller (5/29/2008)

---

I thought the min memory setting had nothing to do with startup value for RAM. SQL Server starts up grabbing whatever memory it needs to start (which...

Best way to see if there's a performance difference - test and measure.

Boise (5/29/2008)

---

I believe you can have IMPLICIT_TRANSACTIONS OFF (which isn't the default and I haven't seen any place...

Pretty much the same. CheckDB can't...

You have corruption in your database. It's corruption in the system tables, so CheckDB is not going to be able to repair.

I don't suppose you know when the corruption occurred...

Is the table perhaps in a different schema than dbo?

18456 is Login Failed. It's usually due to incorrect username or bad password.

Are you using windows authentication or sql authentication?

If windows authentication, are you local admin on the machine ?

Is...

Not switch it. Drop the NC index, drop the primary key, create the clustered index, create the nonclustered...

If you're just doing a single insert, there's no need for an explicit transaction. All statements run within a transaction that starts when th statement starts and autocommits if the...

It's the repeating groups I'm talking about

[LagSpeedGlueUnit1] [int] NULL,

[LagSpeedGlueUnit2] [int] NULL,

[LagSpeedGlueUnit3] [int] NULL,

...

[SteamTemperatureSection1] [int] NULL,

[SteamTemperatureSection2] [int] NULL,

[SteamTemperatureSection3] [int] NULL,

[SteamTemperatureSection4] [int] NULL,

Repeating groups should be split out into separate tables (1NF)....

Then I revise my suggestion - normalise your table.

You've got a very unnormalised design which will make it hard if not impossible to create covering indexes.

Alternative suggestion (that may be...

You certainly should not be truncating the trasdaction log on a regular basis. If you don't care about been able to restore to a point in time, set the recovery...