Reputation
236
Top tag
Next privilege 250 Rep.
View close votes
Badges
2 13
Impact
~7k people reached

  • 0 posts edited
  • 0 helpful flags
  • 15 votes cast
Jan
28
awarded  Notable Question
Nov
12
awarded  Self-Learner
Sep
3
awarded  Popular Question
May
26
awarded  Yearling
Apr
2
awarded  Popular Question
Nov
24
awarded  Popular Question
Jul
2
awarded  Curious
Aug
1
awarded  Teacher
Apr
26
comment Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
I'm working on a script to combine B) and D) right now (I'd rather have them refreshed just in case they may cause problems for us at some point in the future). I'll also recreate this in a new database for your A) suggestion. Thank you! :-)
Apr
26
comment Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
Will do! Thanks again!
Apr
26
comment Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
I'll see if I can create a new database to reproduce this without the complexities of our database muddying up the issues and will see what they have to say about this. Thanks for all of the help!!
Apr
26
accepted Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
Apr
26
comment Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
It's just with these GUID indexes, not all others indexes.
Apr
26
comment Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
I guess that is an idea. Toss that down as an answer and I'll give you a check mark and a smiley face! BTW, something else I just remembered is that when this thing churns, it seems to lock the entire table, even when performed with ONLINE=ON, which I also thought wasn't supposed to happen. Is that correct?
Apr
26
comment Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
Honestly, I can't say if there are major performance problems or not with these indexes. I'm not aware of any perf issues with this, anways. Ultimately, I'm doing an 80/20 attempt at managing indexes. I'm a dev doing DBA work (and obviously, am not the best at it). Ultimately, we do have some indexes that cause very major problems to us if I don't keep them refreshed. Simply rebuilding all indexes that are fragmented has always served us well before. Do you have an alternative strategy for me to follow instead? We have ~450 tables so hand-picking what to rebuild is quite difficult.
Apr
26
comment Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
We query on this column quite a bit when bringing in outside data. Is that what you mean?
Apr
26
comment Composite field in SQL Server, does it exist?
This works well for us. Our requirements are very different than yours but we effectively do this to calculate a datetime column from a few other columns (month number, day number, year number, etc). In our case, the datetime column is only there to assist with queries but are ultimately unimportant.
Apr
26
asked Rebuilding Unique Index with uniqueidentifier in SQL Azure never succeeds
Apr
10
comment How can I remove a bad execution plan from Azure SQL Database?
... doh, sorry, I think you're right! Thanks for correcting me! That's what happens when your wife was expecting you to leave 25 minutes ago... ;-) This script works perfectly for me!
Apr
10
revised How can I remove a bad execution plan from Azure SQL Database?
added 184 characters in body