Viewing 15 posts - 15,421 through 15,435 (of 49,552 total)
Clarification. Unless you're running it with a repair option when there is corruption.
November 29, 2012 at 12:07 pm
sqlfriends (11/29/2012)
So, it doesnot send any kind of alerts to DBA proactively?
If you've configured alerts, you get alerts. If not, you don't (how would SQL intuit who to send alerts...
November 29, 2012 at 10:53 am
CREATE TABLE Blah (
ID int identity,
SomeDate DATETIME
-- other fields
)
CREATE CLUSTERED INDEX idx_Blah on Blah (SomeDate)
ALTER TABLE Blah ADD CONSTRAINT pk_blah PRIMARY KEY NONCLUSTERED (ID)
November 29, 2012 at 10:51 am
What's the error?
Are there any full machine backups running? Possibly via the VM host?
November 29, 2012 at 10:47 am
MOC Ewez (11/29/2012)
November 29, 2012 at 8:20 am
Generally when dealing with a performance problem, knowing what tables are hit often is not very useful. Knowing what queries run often is.
November 29, 2012 at 8:06 am
MOC Ewez (11/29/2012)
Do you do this with or without shoes?:-)
Without of course. 🙂
What you want to do is compare the columns the stats are on and see if you have...
November 29, 2012 at 8:04 am
That's not a useful error. Log the job output to a file and check what's in the file.
You can run integrity checks after taking a backup, but personally I prefer...
November 29, 2012 at 7:15 am
MOC Ewez (11/29/2012)
These are still weak spots for me. I think an overly dramatic...
November 29, 2012 at 7:13 am
aaron.reese (11/29/2012)
November 29, 2012 at 6:22 am
Well, the first thing that anyone trying to help needs to know is what's causing the jobs to fail. What's the error?
November 29, 2012 at 5:53 am
Please don't post multiple threads for the same problem. Can we perhaps keep everything in one thread - http://www.sqlservercentral.com/Forums/FindPost1390289.aspx
November 29, 2012 at 3:52 am
Nic-306421 (11/29/2012)
November 29, 2012 at 3:19 am
Viewing 15 posts - 15,421 through 15,435 (of 49,552 total)