Also after doing the items he listed for 2k if you are using, then do a shrink on the database and log file to force it back down. If you...

My point was to see if the C swap file is corrupt. Not redistribute it. I have seen this can be the case and I feel it is always best...

Which the VB thing or any other encryption method is a waste IMHO, as once it is loded into SQL Server the only encryption you can use is the SQL...

Good luck, and enjoy. Let us know if you get stuck elsewhere or something puzzles you.

Thank you, thank you, I will be here all week.

Try this, go and change the settings of the swap file setting C to 0 and D to the 2 current added together. Could but I doubt be a corruption...

Sorry I don't have a clue about delays with that size database but I would assume it would be up already as I have recovered on a 10 GB db...

Now with paging file filling up on one drive you get drive contention. The data swapping back an forth can actually be your biggest issue. Think of it this way...

That seems to be the only way from the SQL side. But as long as you only have one nic there really is no worry. However I don't know if...

Good catch.

You must have left it in an offline state unless it is extremely large. It is waiting for additional restores. Look at Restore database in SQL books online about this.

...

My bad, extreme appologies.

Like this

CREATE TRIGGER dbo.tr_Name ON dbo.CSDTicket_Info

FOR UPDATE, DELETE AS

INSERT INTO CSDHistory (List.of.columns.with.data.to.fill) SELECT list.to.match.plus.any.variables.such.as.HOST.or.USERNAME.but.defaults.like.GETDATE().I.would.put.on.the.history.table.as.default.for.the.column.they.go.in FROM deleted

Hope that makes sense.

DA NADA (Means Your welcome in spanish).

quote:

---

INNER JOIN creates indexes and the other method doesn't? I didn't get that. Same with OUTER, LEFT and RIGHT JOINS?

---