November 4, 2017 at 4:24 pm
Ed Wagner - Friday, November 3, 2017 10:20 AMI can answer your question about who decided it was a good system. It was the person who was sold a piece of gold, only to find out after the purchase that it was a piece of ____ and that it contains no gold.
Oh, you mean in was a bureaucrat with the job title "Purchasing Manager" or maybe "CFO" who made the decision, someone who understod neither what was needed nor what the crock of <censored> being sold to him was. But an exceptionally bright version of such a bureaucrat, as he got to find out after purchasing the ____ that it wasn't gold, as many of them would be sure the the crock contained really wonderful gold and it was only the people trying to make it work that caused the problems - and they will use the same supplier next time because they provide such wonderfully golden things.
But I don't want to appear too anti-accountant. I've had experience of disasters caused by jumped up accountants who thought their knowledge of accounting enabled them to over-rule experts on engineering and/or logistical decisions, and also the pleasure of working accountants who understood that they didn't know everything. Much like engineers and DBAs, some accountants are dreadful and some are great. Most companies seem to put more store in accountants than in engineers, which can result in dreadful accountants doing a lot of damage; but I've seen dreadfully incompetent engineers in high positions too, and they too do a lot of damage (NOLOCK everywhere; Loops instead of set-oriented - and the loop being in C++ or VB, each iteration calling the database to retrieve or write a single row; and other similar lunacy).
Tom
November 5, 2017 at 6:00 pm
So, today is not what I expected. My dad's right femur broke causing him to fall. He is in the hospital not sure when they will be doing the surgery. Just got back a little bit ago so I could turn off electronics, get his phone, and try to get something to eat. And, before anyone asks, he is 82, all most 83.
November 5, 2017 at 6:26 pm
Lynn Pettis - Sunday, November 5, 2017 6:00 PMSo, today is not what I expected. My dad's right femur broke causing him to fall. He is in the hospital not sure when they will be doing the surgery. Just got back a little bit ago so I could turn off electronics, get his phone, and try to get something to eat. And, before anyone asks, he is 82, all most 83.
Sorry to hear that Lynn. Was there something that caused his right femur to break or did it let go of its own accord? How are you doing with all this?
--Jeff Moden
Change is inevitable... Change for the better is not.
November 5, 2017 at 6:44 pm
Jeff Moden - Sunday, November 5, 2017 6:26 PMLynn Pettis - Sunday, November 5, 2017 6:00 PMSo, today is not what I expected. My dad's right femur broke causing him to fall. He is in the hospital not sure when they will be doing the surgery. Just got back a little bit ago so I could turn off electronics, get his phone, and try to get something to eat. And, before anyone asks, he is 82, all most 83.Sorry to hear that Lynn. Was there something that caused his right femur to break or did it let go of its own accord? How are you doing with all this?
He was moving something, his leg broke, and he fell. I am just glad it happened while I was home. Who knows how long he could have laid there elsewise. His phone was on the counter charging.
Me, freaked a bit because I couldn't find the landline on the counter for about a minute and my phone was downstairs. I do have to say that 911 is a life saver. Right now, trying not cry, hungry but not (even though I have had nothing all day but a Snickers Bar I picked up on the way to the hospital).
November 6, 2017 at 5:17 am
GilaMonster - Friday, November 3, 2017 3:07 PMEd Wagner - Friday, November 3, 2017 10:57 AMLuis Cazares - Friday, November 3, 2017 10:40 AMJoe’s Big Deal: the vNext query processor gets even better. Joe, Kevin Farlee, and friends are working on the following improvements:
- Table variable deferred compilation – so instead of getting crappy row estimates, they’ll get updated row estimates much like 2017’s interleaved execution of MSTVFs. >
- Batch mode for row store – in 2017, to get batch mode execution, you have to play tricks like joining an empty columnstore table to your query. vNext will consider batch mode even if there’s no columnstore indexes involved. >
- Scalar UDF inlining – so they’ll perform like inline table-valued functions, and won’t cause the calling queries to go single-threaded. >
The inlining SF looks very promising. Then again, a lot of SQL 2017 looks great. I'll believe it when I test it. 😉
Inline scalar UDFs is not SQL 2017. It's future.
Got it. Thanks, Gail. I'll still believe it when I test it.
November 6, 2017 at 5:25 am
GilaMonster - Friday, November 3, 2017 3:07 PMEd Wagner - Friday, November 3, 2017 10:57 AMLuis Cazares - Friday, November 3, 2017 10:40 AMJoe’s Big Deal: the vNext query processor gets even better. Joe, Kevin Farlee, and friends are working on the following improvements:
- Table variable deferred compilation – so instead of getting crappy row estimates, they’ll get updated row estimates much like 2017’s interleaved execution of MSTVFs. >
- Batch mode for row store – in 2017, to get batch mode execution, you have to play tricks like joining an empty columnstore table to your query. vNext will consider batch mode even if there’s no columnstore indexes involved. >
- Scalar UDF inlining – so they’ll perform like inline table-valued functions, and won’t cause the calling queries to go single-threaded. >
The inlining SF looks very promising. Then again, a lot of SQL 2017 looks great. I'll believe it when I test it. 😉
Inline scalar UDFs is not SQL 2017. It's future.
Got it. Thanks, Gail. I'll still believe it when I test it.
November 6, 2017 at 5:33 am
Lynn Pettis - Sunday, November 5, 2017 6:44 PMJeff Moden - Sunday, November 5, 2017 6:26 PMLynn Pettis - Sunday, November 5, 2017 6:00 PMSo, today is not what I expected. My dad's right femur broke causing him to fall. He is in the hospital not sure when they will be doing the surgery. Just got back a little bit ago so I could turn off electronics, get his phone, and try to get something to eat. And, before anyone asks, he is 82, all most 83.Sorry to hear that Lynn. Was there something that caused his right femur to break or did it let go of its own accord? How are you doing with all this?
He was moving something, his leg broke, and he fell. I am just glad it happened while I was home. Who knows how long he could have laid there elsewise. His phone was on the counter charging.
Me, freaked a bit because I couldn't find the landline on the counter for about a minute and my phone was downstairs. I do have to say that 911 is a life saver. Right now, trying not cry, hungry but not (even though I have had nothing all day but a Snickers Bar I picked up on the way to the hospital).
Sorry to hear Lynn. Hope that he has a speedy, and unproblematic, recovery.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 6, 2017 at 6:22 am
Lynn Pettis - Sunday, November 5, 2017 6:44 PMHe was moving something, his leg broke, and he fell. I am just glad it happened while I was home. Who knows how long he could have laid there elsewise. His phone was on the counter charging.
Me, freaked a bit because I couldn't find the landline on the counter for about a minute and my phone was downstairs. I do have to say that 911 is a life saver. Right now, trying not cry, hungry but not (even though I have had nothing all day but a Snickers Bar I picked up on the way to the hospital).
So sorry Lynn. Here's hoping he gets better real soon.
"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
November 6, 2017 at 6:25 am
Lynn, ditto to the last two posts. You and your family are in my thoughts and I'm sending as many best wishes your way as possible.
November 6, 2017 at 7:25 am
Lynn that is scary. Glad you were there to be able to help. Hoping for a speedy recovery.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
November 6, 2017 at 8:42 am
Sorry, Lynn. Hope he heals and you recover.
Ping the SQL community if you need something. I'd say me, but I'm leaving town again. But, ping me if I can help.
November 6, 2017 at 9:35 am
Lynn Pettis - Sunday, November 5, 2017 6:00 PMSo, today is not what I expected. My dad's right femur broke causing him to fall. He is in the hospital not sure when they will be doing the surgery. Just got back a little bit ago so I could turn off electronics, get his phone, and try to get something to eat. And, before anyone asks, he is 82, all most 83.
Best of luck mate, hope everything goes well!
😎
November 6, 2017 at 10:06 am
There are some days I really hate our Vendor system...
One of my biggest bug bears is how it handles field name changes on SQL's side. When someone realises they need to change the data type of a field, they rename the existing field, then create a new field with the old name, then commit (they can't change the data type directly, so this does make sense). How does it handle it on SQL? Well, firstly, it drops the dependant objects (views, SPs, etc), then it tries to create the "new" column (good, that fails bceause the column already existrs), then renames the old column, then recreates the views and SPs with a column name that doesn't exist! ARGH. Thus anything referencing the table fails because the INSERTs can't put data into a column that doesn't exist, and the views and SPs fail too for the same reason.
Only way to fix it? Tell the Vendor Application to BULK INSERT the data; but you can't tell it to do just that one table, no... You have to do EVERYTHING... Because I love taking our main application offline for 2-3 hours... Love it... /headdesk
</rant>
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 6, 2017 at 11:08 am
Lynn Pettis - Sunday, November 5, 2017 6:44 PMJeff Moden - Sunday, November 5, 2017 6:26 PMLynn Pettis - Sunday, November 5, 2017 6:00 PMSo, today is not what I expected. My dad's right femur broke causing him to fall. He is in the hospital not sure when they will be doing the surgery. Just got back a little bit ago so I could turn off electronics, get his phone, and try to get something to eat. And, before anyone asks, he is 82, all most 83.Sorry to hear that Lynn. Was there something that caused his right femur to break or did it let go of its own accord? How are you doing with all this?
He was moving something, his leg broke, and he fell. I am just glad it happened while I was home. Who knows how long he could have laid there elsewise. His phone was on the counter charging.
Me, freaked a bit because I couldn't find the landline on the counter for about a minute and my phone was downstairs. I do have to say that 911 is a life saver. Right now, trying not cry, hungry but not (even though I have had nothing all day but a Snickers Bar I picked up on the way to the hospital).
Deepest sympathy, Lynn. I hope the surgery will be soon and successful. A broken femur at that age is a real problem.
Tom
November 6, 2017 at 11:12 am
Ed Wagner - Friday, November 3, 2017 10:57 AMLuis Cazares - Friday, November 3, 2017 10:40 AMJoe’s Big Deal: the vNext query processor gets even better. Joe, Kevin Farlee, and friends are working on the following improvements:
- Table variable deferred compilation – so instead of getting crappy row estimates, they’ll get updated row estimates much like 2017’s interleaved execution of MSTVFs. >
- Batch mode for row store – in 2017, to get batch mode execution, you have to play tricks like joining an empty columnstore table to your query. vNext will consider batch mode even if there’s no columnstore indexes involved. >
- Scalar UDF inlining – so they’ll perform like inline table-valued functions, and won’t cause the calling queries to go single-threaded. >
The inlining SF looks very promising. Then again, a lot of SQL 2017 looks great. I'll believe it when I test it. 😉
The TV deferred compilation looks interesting too. I wonder when we'll see SQL 2018.
Tom
Viewing 15 posts - 60,286 through 60,300 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply