Viewing 15 posts - 37,741 through 37,755 (of 49,566 total)
Interesting. Last cluster patching I did was 2005. I knew the install for the cluster had changed in 2008, didn't realise the patch had changed too.
July 10, 2009 at 3:07 pm
ken.trock (7/10/2009)
Yes, this little update is within a larger transaction that does a lot of updates elsewhere in the DB. But it need not be I think.
So the lock...
July 10, 2009 at 3:05 pm
Just one question. Why are you patching the two nodes separately? SQL is cluster aware and should be able to patch both nodes with you run the patch on the...
July 10, 2009 at 2:32 pm
I'd suggest calling customer support at this point.
July 10, 2009 at 2:18 pm
If the indexes are selective, the updates should be quick and the blocking short-lived, especially if, as you say, the underlying table is rarely if ever changed.
Can you check and...
July 10, 2009 at 2:02 pm
ed (7/10/2009)
July 10, 2009 at 2:01 pm
What are the indexes on the RollupHistory table and what does the update statement look like? Inadequate indexing is often a major cause of blocking in SQL.
July 10, 2009 at 12:42 pm
mahesh.vsp (7/10/2009)
But one thing i got stucked is when the Log is full then it shouldnt allow any more DML operations.
Bear in mind that not all log entries are...
July 10, 2009 at 12:32 pm
Google tells me that the Intel Xeon E5440 is a quad core processor
http://www.google.com/search?q=Xeon+%2BE5440+site%3Aintel.com
First hit on that search page is
http://processorfinder.intel.com/details.aspx?sSpec=SLANS
Considering that device manager shows the total cores, not the total physical...
July 10, 2009 at 12:26 pm
Elliott W (7/10/2009)
Now on that dateadd/convert question, I fully agree yours works, the only thing I'd be questioning is which performs better..
http://sqlinthewild.co.za/index.php/2008/09/04/comparing-date-truncations/
July 10, 2009 at 9:33 am
Two that irritate me to no end and that I see far too often are running checkDB with a repair option and deleting the transaction log.
CheckDB with the REPAIR_ALLOW_DATA_LOSS option...
July 10, 2009 at 9:05 am
river (7/10/2009)
July 10, 2009 at 7:09 am
Decimal(5,5) means a number that has 5 digits in total and 5 on the right hand side of the decimal place. Hence it cannot allow any number larger than .99999...
July 10, 2009 at 5:58 am
There's no such syntax. If you want to compare to all the columns, you have to explicitly compare to all columns.
So, in this case
SELECT Name, Age, Description, Field1, Field2
FROM MyTable
WHERE...
July 10, 2009 at 5:19 am
The remote timeout setting affects remote servers only. It has no effect on how long queries will wait on the local server.
If you want the alter database to kick everyone...
July 10, 2009 at 5:15 am
Viewing 15 posts - 37,741 through 37,755 (of 49,566 total)