It does look like someone (or several someones) is running a brute-force hack attempt against your serves. Can you speak to your network people, see if they can block ip...

They will affect any query that tries to use the corrupt pages. Update stats (unless used with fullscan) samples pages, so it may or may not be affected, depending which...

500kb of output even with no_infomsgs? Wow.

If the errors are in the base tables, and you have no clean backup, then your only option is to run checkDB with the...

That could well be a hack attempt.

What's the previous line in the error log? (specifically the state?)

How strong is your sa password? If you're not using the account, can you...

As for the first, I don't think that's logged.

For the second, query the sysjobhistory table in msdb. The amount of history depends on the frequency of the job. I think...

Why do you need a cursor? Unless you're doing certain types of admin tasks (which are often one object at a time)...

Raghavender (9/28/2008)

---

Output of the Checkdb is as below:

CHECKDB found 0 allocation errors and 85 consistency errors in database 'DBNAME'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC...

saby (9/26/2008)

---

i want to shrink my log size to 100 mb but the issue is can i use this command BACKUP LOG {DatabaseName} WITH NO_LOG as my recovery model is...

The other thing I will suggest is that you consider moving the clustered index to the date column or the ID column (mainly because it will fragment less)

and put...

The first thing I will suggest is that you do an update stats with full scan on that table.

The execution plan shows that the optimiser is estimating 1 row and...

If you're able to upload the permon stuff, please not as a screenshot. There's not enough info in a screen shot. Zip and upload whatever you saved (if possible)

Where's the clustered index?

What are the primary keys?

Is that the only query that will be run on the tables?

What's running on Node A?

The error indicates that there's not enough memory to bring SQL online, which indicated that something else is running and is consuming the memory.

Have you limited the server's max memory? If not it would be a very good idea to do that. Set the max memory to around 29GB.

Also have a look at...

Can you post the execution plan please (saved as a .sqlplan file, zipped and attached to your post)

Also, you say it's slow. What do you mean by slow? (5 sec,...