Timothy Ford (7/10/2009)

---

I would have to agree with Lynn. I see no problems here. If you would feel better limiting the memory for SQL I would set the...

I guess I'm trying to figure out what the problem is, you have 32 GB of RAM and SQL Server is only using 10 GB. Does not equate to...

What else is running on the server? Is it dedicated to SQL Server?

zenrigar (7/10/2009)

---

Oh then that was the trick, thanks alot for the explanation :w00t:

i also checked the link of your post and it was helpful too, now im curious about...

I'd have to Google those. I haven't looked at them. They are supposed to be able to read the transaction log and help recover lost data or database...

I agree, Alvin.

Something you should be aware of, trying hide your mistake makes the mistake even bigger. It is best to admit the error and get help fixing it.

You aren't going to be able to fix this yourself if you can't access the backups. As Jeffery said, you will need to get help. With access to...

On a totally different subject, Anyone hear from Bob lately? Haven't seen him on SSC for a while.

What is your current recovery model? If you had to, can you get the most current backup that, you unfortunately say can't at the moment, exists?

You have never taken a full backup of the database, not even when it was first created?

What type of situation are you trying to emulate? A disk failure where you have lost the entire ldf file?

Or, perhaps, if starts into a flame war? Hopefully not. And it stays away from the personal attacks as well.

John Rowan (7/10/2009)

---

Ha! I'll have to second that one. Not just in forums, but this one...

I have to ask, please try the following queries:

SELECT

*

FROM

Tab2 t2

INNER JOIN Tab3 t3

...