Reputation
223
Top tag
Next privilege 250 Rep.
View close votes
Badges
2 9
Impact
~5k people reached

  • 0 posts edited
  • 0 helpful flags
  • 6 votes cast
Jan
29
awarded  Nice Question
Jan
28
accepted SQL Server VARCHAR Column Width
Jan
28
comment SQL Server VARCHAR Column Width
This is good information. There is a disadvantage of underestimating the size of a column, in that refactoring will have to take place if it turns out that the initial estimate was wrong, and longer data cannot be (fully) stored until such refactoring takes place.
Jan
28
comment SQL Server VARCHAR Column Width
@marc_s: According to a webinar by Brent Ozar, a VARCHAR(max) can also be included in a clustered index. The example he used was the user's table of Stack Overflow. i.brentozar.com/engine.pdf
Jan
5
awarded  Yearling
Jan
5
comment Zero rows updated while archiving rows
Thank you both for the advice.
Jan
5
comment Zero rows updated while archiving rows
I just noticed that I was not including the Id in the column specification, and the target table was not configured to automatically assign one. I guess that results in an error somewhere in the SQL stack. Is that error logged/recorded? Is it possible to see that error in any way?
Jan
5
asked Zero rows updated while archiving rows
Oct
29
awarded  Notable Question
Sep
24
awarded  Autobiographer
Feb
27
comment Estimating IO Requirements for Bursty Usage
I'll have to get some statistics on the overall size of the index and the percentage of that index typically accessed by a given query to answer your question.
Feb
27
comment Estimating IO Requirements for Bursty Usage
@JackDouglas: The largest reads are via an indexed view, such that the WHERE clause corresponds to the index, but returning more data than just what is in the index. I'm not sure what that means for the degree of sequential IO. Since the underlying IO subsystem is AWS EBS, I'm not sure how that impacts physical access.
Feb
26
comment Estimating IO Requirements for Bursty Usage
@JackDouglas: This is 98% reads. There is a trickle of writes.
Feb
26
accepted Estimating IO Requirements for Bursty Usage
Feb
26
comment Estimating IO Requirements for Bursty Usage
@MikeFal: Do you have any thoughts on the testing methodology specifically for this bursty pattern? Just run a single query and watch the counters in question? Run a number of the (normally periodic) queries one after another, watching the counters?
Feb
26
awarded  Commentator
Feb
26
comment Estimating IO Requirements for Bursty Usage
Thank you for the detailed answer. AWS now has a premium feature called Provisioned IOPS that ensures that the purchased number of IO operations per second can be performed 99.9% of the time. I think an IO operation is defined as reading or writing a 16K block of data.
Feb
26
asked Estimating IO Requirements for Bursty Usage
May
30
awarded  Popular Question
Apr
3
accepted Executing sys.dm_fts_parser without sysadmin server role