« first day (2259 days earlier)      last day (2626 days later) » 

12:00 AM
I looked at the rextester link and nearly hit "fork it" then realized I had misread the label.
 
what's the significance of the 10X?
 
@AndriyM I'm not sure I understand what you mean. That temp tables are useless in MySQL?
 
in Discussion on answer by Brent Ozar: Is there any way to fix reputation mechanics here? on Meta Stack Exchange Chat, Feb 16 at 20:30, by Matthew Sontum
10xer means that I produced 10x as much usable code (as measured by the number of objects checked into source control) as the average person in my group (not including me) We also had a ticketing system in which I closed 2.5x as many tickets as the next best person. Note that this was before I got into management. But even with my management duties I was still the top ticket closer and object contributor, just not as far ahead of the next best person.
 
ah, that guy
 
That Guy.
 
12:03 AM
"The suspension period ends on Sep 7 at 19:21."
guess I missed something
I'm ok with that
 
@ypercubeᵀᴹ Not as useful as I thought.
 
@PaulWhite I would prefer to do self-Q & A (since it would be easier to do), but I think that some of this stuff would be "too localized"
 
@JoeObbish Don't be bothered by the literal wording of the close reasons. The community applies the rules. If it's good and useful, I expect it will be up voted and left open.
 
In other words, voted up and open left.
 
Quite.
 
12:07 AM
My hesitation comes from not quite understanding how some of the rules work, I think
And posting a question that gets closed could be a moderate waste of time for some folks
 
The rules exist to prevent/remove stuff we don't want or which is harmful to the community. If it's judged on topic and useful it stays.
I think we do quite well at only closing/deleting stuff that is quite frankly crap. (which includes stuff that would be good elsewhere, but doesn't fit Q & A style).
 
Ohhh
 
The other thing I'd say is that asking a question is good, even if you intend to self answer, because someone else may have a better answer you hadn't considered.
 
I am now feeling encouraged to ask more questions, thank you
 
 
4 hours later…
3:49 AM
I'm having trouble believing this, but it looks like SMALLINT and TINYINT take up the same amount of space in SQL Server...
 
@JoeObbish huh?
 
@PaulWhite I was going through the motions to post a proper answer for this: dba.stackexchange.com/questions/166815/…
I even dumped one of the full data pages for each table and it looked similar (to my untrained eye)
 
@JoeObbish There is a minimum row length. I forget if it is 7,8, or 9. It's 9.
 
ohhhh
thanks, I was wondering why the row size was so large
 
9
A: SQL SERVER Storage of TinyInt

Remus RusanuIf you compute the record using the simple size addition you indeed get 8: 4+1+2+1 (header+fixed size+null bitmap count+ null bitmap itself). But a heap record cannot be smaller than the forwarding stub size, which is 9 bytes, since the record must guarantee that it can be replaced with a forward...

 
3:58 AM
yeah, just added a CHAR(7) and got the expected result
 
> But a heap record cannot be smaller than the forwarding stub size, which is 9 bytes, since the record must guarantee that it can be replaced with a forwarding stub.
That's the reason I was struggling to remember.
 
that's interesting
so you can create tables in which adding a column with data does not increase total size
of course, you're a bit limited in your options there
 
Yeah there's some 'free' space effectively, at least with rowstore.
I have no idea if there is a minimum size for columnstore.
 
was going to do a CCI example too
so I'll poke around a bit
 
Have fun :)
 
4:15 AM
data: 160 KB
I suppose it would compress well...
that's for 10M rows and 10 columns, so if there is a limit it's very small
will poke around more
not really proof, but suggestive I think? dbfiddle.uk/…
 
4:46 AM
@JoeObbish I would build the CSI after the data, with maxdop = 1 to eliminate some per-thread effects. dbfiddle.uk/…
32KB seems a good guess, but I really don't know.
 
5:09 AM
@PaulWhite hard to know if sp_spaceused works perfectly with CCI
I can get 24 KB for one column and 8 KB for an additional "empty" column: dbfiddle.uk/…
have a good evening
 
@JoeObbish As far as I know it does.
1
A: Most efficient data type for a column storing numeric values between 0 and 100

Joe ObbishThis answer only covers SQL Server. The answer depends on how you define efficient: is it space or CPU? There can be a tradeoff between the two. Let's start by checking the documentation for data types that store integer data: ╔═══════════╦═══════════════════════════════════════════════════════...

 
 
8 hours later…
1:17 PM
Boy that CCI is getting some great compression.
 
1:52 PM
Indeed, it's a whole new era for storing integers from 0-100!
2
 
 
5 hours later…
7:20 PM
0
Q: How to include a detailed response to a detailed answer

WilsonI have a question (Cross join on a numbers table to get line vertices, is there a better way?) where I received a very thorough/detailed answer. The answer wasn't so much an answer as it was a series of questions. I found the answer to be immensely helpful, and thought it was only fair to post m...

 
 
2 hours later…
9:39 PM
@PaulWhite I've added 'binary', 'image' and 'timestamp' to the list of types to convert to hex (which works fine), but the hierarchyid,geometry and geography types have me stumped. Rather than just failing, it now returns the typename which is still pretty useless
I might have to ask a question on SO!
2
 
10:25 PM
1
Q: DBA SE graphic design: Who did it, and what else have they done?

WilsonI've always enjoyed the graphic design of the DBA SE header: Who made it and what else have they done? I like it and want to see more.

 
Lost in the mists of time. But I still have the stickers.
 
 
1 hour later…
11:35 PM
0
Q: SQL Performance Gap Between SELECT WHERE IN (1,2,3,4) vs IN (select * from STRING_SPLIT('1,2,3,4',','))

raeldorI seem to be having a huge performance gap between using hard coded values for a SELECT IN, vs a STRING_SPLIT. The query plans are identical except for the last phase where the index seek is getting executed multiple times for the STRING_SPLIT code. The outcome is a CPU time of about 90000 vs a...

It is a SO question, I suggested to the OP to move it to dba.
 

« first day (2259 days earlier)      last day (2626 days later) »