Are the posted questions getting worse?

  • Honestly the biggest gripe with Azure VMs (where we are now) is the lack of flexibility in drive sizing.  It's all multiples of 64, so 64 / 128 / 256 / 512 / 1024 / 2048GB.  If you only really need another 128GB or so to carry on for another couple years, you're either looking at going to, say, a 1TB drive from your 512GB, or going to route of moving around data files (with an outage.)

    One of the nice things about Azure VMs is the lack of flexibility in drive sizing, too.  Being multiples of 64, it does tend to mean when you need only a bit more space, you're going to get a lot more space and not need to muck around any time soon trying to get more space, plus the size increase is a painless, zero-downtime process that with our apps can be done during normal business hours without the end-users noticing...

  • Thom A wrote:

    jasona.work wrote:

    Anyone noticing a round of replies to posts that "feel" suspiciously like someone fed the OP's question into one of the chat-bot AIs and posted the "answer"?

    It's not an uncommon problem. I'm finding it harder and harder to trust content (I don't just mean here), from people who weren't active 5 or more years ago, where I can at least see that they knew what they were talking about then, and so hopefully their recent content is also original. There's a lot of sites that are getting responses copied verbatim from AI, without denoting it's by AI (which most of them strongly suggest/require you do when copying from them).

    If it helps any, I've distrusted content from a lot of "experts" that have 20 years or more on the books for a very long time and that became even more acute on Monday, 18 Jan 2016 and has only gotten worse since then.  That especially includes people who write documentation for SQL Server.  For example, here's a quote from the DATETIME documentation located at...

    https://learn.microsoft.com/en-us/sql/t-sql/data-types/datetime-transact-sql?view=sql-server-ver16#convert-other-date-and-time-types-to-the-datetime-data-type

    Does anyone at all see anything wrong with that? 😉

     

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • It's the middle of the night and I'm online for "reasons."

    Looking at your link, Jeff, somebody didn't proofread their code or didn't care. Samples 1 & 4 are identical code. There's ... no point to the ISO comments?

    I do remember you making a stink about datetime2, but I'm too tired to recall it. Also, why the heck are they using different dates to make their point? Do the same datetime values not make it for them?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Eirikur Eiriksson wrote:

    Michael L John wrote:

    The infrastructure folks created an arbitrary set of standards for free space.

    So you are forced to write SQL shorthand... 😉 😎

    This always bothers me when one cannot spend $ to keep $$$$ business running.........

    One aspect of this that I've seen is that as we've moved data from on prem servers(think SAP Hana) to Snowflake, the actual costs are now visible to more people and they start fainting at the numbers. It's cheaper than the on prem stuff was, but those costs were not visible to anyone so no one cared.

  • Brandie Tarvin wrote:

    It's the middle of the night and I'm online for "reasons."

    Looking at your link, Jeff, somebody didn't proofread their code or didn't care. Samples 1 & 4 are identical code. There's ... no point to the ISO comments?

    I do remember you making a stink about datetime2, but I'm too tired to recall it. Also, why the heck are they using different dates to make their point? Do the same datetime values not make it for them?

    If you look at the code I posted, the text to describe what happens says that "When the fractional precision of the datetime2(n) value is greater than three digits, the value is truncated."

    Now... run the following code and see.  I even changed the problem to use the same datatype (DATETIME2) with just one digit less resolution...

    DECLARE @datetime2 DATETIME2(4) = '1968-10-23 12:45:37.1237';
    SELECT CONVERT(DATETIME2(3),@datetime2);

    See the problem?  If not, try the following code...

    DECLARE @datetime2 DATETIME2(4) = '2022-12-31 23:59:59.9995';
    SELECT CONVERT(DATETIME2(3),@datetime2);

    What's really a disappointment is that it used to be correctly documented and this problem is one of the reasons why they had to come out with DATETRUNC().

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden wrote:

    If you look at the code I posted, the text to describe what happens says that "When the fractional precision of the datetime2(n) value is greater than three digits, the value is truncated."

    Now... run the following code and see.  I even changed the problem to use the same datatype (DATETIME2) with just one digit less resolution...

    DECLARE @datetime2 DATETIME2(4) = '1968-10-23 12:45:37.1237';
    SELECT CONVERT(DATETIME2(3),@datetime2);

    See the problem?  If not, try the following code...

    DECLARE @datetime2 DATETIME2(4) = '2022-12-31 23:59:59.9995';
    SELECT CONVERT(DATETIME2(3),@datetime2);

    What's really a disappointment is that it used to be correctly documented and this problem is one of the reasons why they had to come out with DATETRUNC().

    This is why I like the docs being online and editable with a PR. I try to correct stuff like this because the devs (or doc people) often don't really pay attention or don't know how things work.

     

    I'll try to find time to PR this thing and clean it up.

  • Is there any way to update the Recent comments

    i.e.

    Recent comments

    Specialist qualification for care professionals supporting those with advanced dementia or terminal ...

    Accesssskills

    when the underlying comment gets marked as spam?

    412-977-3526 call/text

  • Anyone on the observability train here? I keep reading about it and seeing stuff about it, and this explanation almost seems to go in circles: https://www.honeycomb.io/blog/observability-telemetry-monitoring

  • Steve Jones - SSC Editor wrote:

    Anyone on the observability train here? I keep reading about it and seeing stuff about it, and this explanation almost seems to go in circles: https://www.honeycomb.io/blog/observability-telemetry-monitoring

    That's because if you observe it, you can only know the performance, but not the direction. Signed, Heisenberg

    -------------------------------------------------------------------------------------------------------------------------------------
    Please follow Best Practices For Posting On Forums to receive quicker and higher quality responses

  • jasona.work wrote:

    Anyone noticing a round of replies to posts that "feel" suspiciously like someone fed the OP's question into one of the chat-bot AIs and posted the "answer"?

    Yes... especially due to the flagrant plagiarism of code.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Steve Jones - SSC Editor wrote:

    Jeff Moden wrote:

    If you look at the code I posted, the text to describe what happens says that "When the fractional precision of the datetime2(n) value is greater than three digits, the value is truncated."

    Now... run the following code and see.  I even changed the problem to use the same datatype (DATETIME2) with just one digit less resolution...

    DECLARE @datetime2 DATETIME2(4) = '1968-10-23 12:45:37.1237';
    SELECT CONVERT(DATETIME2(3),@datetime2);

    See the problem?  If not, try the following code...

    DECLARE @datetime2 DATETIME2(4) = '2022-12-31 23:59:59.9995';
    SELECT CONVERT(DATETIME2(3),@datetime2);

    What's really a disappointment is that it used to be correctly documented and this problem is one of the reasons why they had to come out with DATETRUNC().

    This is why I like the docs being online and editable with a PR. I try to correct stuff like this because the devs (or doc people) often don't really pay attention or don't know how things work.

    I'll try to find time to PR this thing and clean it up.

    I was done being a "free employee" for Microsoft a long time ago.  Seriously... don't they have anyone that actually understands how to test things INCLUDING but not limited to "Edge Cases"?

    My greatest understanding of how little MS actually understands about the world of databases is when Erland Sommarskog submitted his infamous request about a sequence generator. The first reaction from the people at Microsoft basically asked what anyone would need such a thing for.  They had no clue even though PostGres had such a function for quite a while at that time.

    And then you have the infamous STRING_SPLIT() function that came out in 2016 without an ordinal for the returns and didn't bring that on until 6 years later.  Seriously?  It's not like the idea was new.

    They won't even talk with their own people.  I'm still convinced they have no clue about how powerful the PIVOT expression is in MS Access.  Why didn't they use that for a model to begin with.

    And then came the performance devastation that arrived with 2019 and has persisted into 2022.  They still haven't fixed that.  Unfortunately, it would not be in good form for me to name the MS people that I've talked to on that subject there. Just like when I jumped in on Erland's Connect item to explain the wide array of things that it would be used for, me saying something wouldn't fix the people, er.. I mean, the problem.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Some days I am not a fan of my employer...

    Put in the paperwork to get a trip to Summit covered for this year, but because the head honcho is leaving in a month or so and we're getting a new one, it's not been approved, and that's IF the restriction on travel that was put in from even higher up the food chain gets lifted or at least "lightened."

    Drives me nuts because I like to plan ahead (way, way ahead, I'm already planning vacations in 2026 and 2027)

    I'd start buying things for Summit like my badge now on my nickle, but if I do that and the trip gets approved, it's "so sorry you used your own money, we can't reimburse you for it even though we're now going to be paying for everything"

    sigh...

    OK, pity party over.

  • Corporate budgets can be crazy. I hate that kind of stuff

  • Sorry to hear it Jason. Best of luck. My son is now traveling for work for a giant corporation. He's reminding me why I like working for smaller companies. He was under budget for the day, but over budget for a meal, so they dinged him on an expense report. Just ridiculous.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Steve, Grant, thanks.  At least if (when, I hope) the conference gets approved, I don't have to worry as much about daily budgeting, we've got a fairly (well, last year, this year could be different) lax budget policy.

    Daily is a per-diem for meals and incidentals and it's easy enough to stay under that.

    Of course, the further complication to this is, the conference could get approved, but because it's in the next fiscal year, the budget might not be there for it...

Viewing 15 posts - 66,766 through 66,780 (of 66,802 total)

You must be logged in to reply to this topic. Login to reply