What If Week: SQL Server Code Review

Top Secret

For the sake of any lawyers out there reading, I want to start by saying we do not now, nor have we ever possessed SQL Server’s source code.

I wouldn’t even know what to do with it if I did — I doubt it’s written in crayon.

Heck, I’m not even competent enough to use a debugger, though I have tried. Bob Ward and Paul White just make it look so glamorous.

With that out of the way, let’s pretend we did, for some reason. Say something like:

  • SQL Server went open source
  • You got a job at Microsoft working on it
  • The source code leaked

And now we can pretend that we’re competent code readers and writers and start flipping through the pages (these things are like books, right?).

Topical Thunder

This week, we’ll run a series of short blog posts asking you, our dear and beloved readers, what parts of the code you’d want to get a gander at in different scenarios.

Why this series? Why this week? Because Brent is converting us into an offshore team we’re on a cruise in Alaska, and this is a nice time for you to discuss things among yourselves without moderation. Or moderators.

Bear with me

Hopefully WordPress sends them all out on schedule!

Previous Post
Abstracts Open for GroupBy December
Next Post
What If Week: What Would You Look At First?

8 Comments. Leave new

  • I would like to see the bulk import/export operations code. I was always fascinated how on the earth the SSIS is inserting zillions of records into a table in milliseconds

  • We’d finally have a way to create a comprehensive list of every trace flag and what exactly they do.

    • True. And a list of Error and Severity codes

    • Yes, I would LOVE to know what is within that damn 4199TF that I had to turn on to regain performance for a boat load of functions we have, and why it is affecting the TFS builds now (we have to turn it off then back on to get TFS to do a build on some databases).

  • We could finally write our own HotFix patch for The Damn Vague “String or binary data would be truncated” Error, to ACTUALLY TELL US THE COLUMN THAT’S BREAKING!


    • That would be extremely helpful. Add on to that the column length, the data length and the damn row number.

  • I would love to see the code that determines the work load for each CPU when code goes parallel. ‘Cuz if it worked properly, we would not have as many waits.

  • Alexander Gay
    August 16, 2017 3:03 am

    I’d like to see the TFS/VSTS source control integration code, as a nice, simple, built-in source control option would be nice.
    But so would the ability to create custom skins for SSMS. This is a common feature in FOSS that I would like to see more of.