meta user
network profile
|
Apr 11 |
answered | Database user permissions: GRANT VIEW DEFINITION but DENY on some object types |
|
Apr 10 |
asked | Database user permissions: GRANT VIEW DEFINITION but DENY on some object types |
|
Mar 28 |
accepted | Query notifications and connection options |
|
Mar 28 |
answered | Query notifications and connection options |
|
Mar 28 |
comment |
Programmatically find indexes that cannot be rebuilt online Thanks all. I've used this method for now. I've looked at Ola's scripts. The problem I was originally grappling with was massive log bloat during index rebuild, so I'm trying an approach of rebuilding the 20 worst indexes at a time - I couldn't figure out how to incorporate this into Ola's script just yet. |
|
Mar 28 |
accepted | Programmatically find indexes that cannot be rebuilt online |
|
Mar 27 |
asked | Programmatically find indexes that cannot be rebuilt online |
|
Feb 20 |
comment |
Query notifications and connection options It's the same application, same connection string, hence the confusion. |
|
Feb 19 |
comment |
Query notifications and connection options Don't understand why most connection are being made as read committed but these particular connections are read uncomitted |
|
Feb 19 |
asked | Query notifications and connection options |
|
Dec 17 |
comment |
ASPState database locking and growth problems Blocking is being investigated as one possible cause of the intermittent poor performance. I'm really interested to understand why the same session would be getting updated so frequently. |
|
Dec 14 |
accepted | Non-clustered Index Update not displayed in execution plan |
|
Dec 14 |
awarded | Commentator |
|
Dec 14 |
comment |
ASPState database locking and growth problems Looks like they may have. We had to add the randomise bit. |
|
Dec 14 |
comment |
ASPState database locking and growth problems Interesting suggestion, but the cursor is actually part of the official MS stored proc, not something that has been added. |
|
Dec 14 |
comment |
ASPState database locking and growth problems Hmm. fairdoos. The jobs won't overlap, and I don't think it get's called from anywhere else. But adding TOP 10 will just make blocking worse. At present the cursor ensures that only one record is deleted at a time, right? |
|
Dec 14 |
comment |
ASPState database locking and growth problems Because the procedure runs for > 1 minute at busy times, there is the danger that 2 copies of the proc are trying to delete the same row, the ordering by NEWID reduces the chance of this. |
|
Dec 14 |
asked | Non-clustered Index Update not displayed in execution plan |
|
Dec 14 |
comment |
ASPState database locking and growth problems We have implemented the following recommendation: aspalliance.com/articleViewer.aspx?aId=1184&pId=-1 |
|
Dec 14 |
comment |
ASPState database locking and growth problems Background to session state is here: msdn.microsoft.com/en-us/library/aa478952.aspx |
