Are the posted questions getting worse?
- MVDBA (Mike Vessey) wrote:Michael L John wrote:Jeff Moden wrote:MVDBA (Mike Vessey) wrote:Michael L John wrote:
Is this a good example of someone who may have picked the wrong thing to do with their lives?
https://www.sqlservercentral.com/forums/topic/ssis-package-error-22
oh man i wish i was in that stream ... jeff can be quite direct.
Is that good or bad? 😀 I thought I was pretty nice about saying that he needs to slow down and read his code... especially in the areas that SQL Server was telling him to look.
His last post was the kicker. "The files empty". Uh, duh, did you fill it with anything?
good lad jeff.. you aren't dropping your standards
Heh... that wasn't me. That was Michael.
Seriously, though... I come across that tough? I thought I reserved that for JC.
--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) - Michael L John wrote:
I'm dealing with a crappy proc, and a crappy design, right now.
The devs did the "Code first" design. In other words, the ORM designed the database for them.
I can't post the code for the biggest offending proc, I don't feel like taking the time to obfuscate it. But, it does 16 selects into a temp table, of the same tables, with slightly differing WHERE clauses. it then selects distinct into another temp table, and then finally does a count and group by to get a count of each item.
There are 10 tables in this database. There are FORTY unused indexes in it. The devs keep trial and erroring adding indexes.
I could go on and on, but my fingers would get tired.
code first=don't care about database- someone elses problem
MVDBA
- Jeff Moden wrote:
Seriously, though... I come across that tough? I thought I reserved that for JC.
nah, i know you are a big cuddly teddy bear underneath - now get back to be being meaner than jc... then i can rest easy knowing i'm the nice DBA - you could almost make the 7 dwarves out of us... Scary, mean,nice,ISO,little,shirts I just need one more 🙂
MVDBA
-
I can't remember who, but I remember someone in here saying that they were having problems with Powershell Core because of it's changed (lack of) functionality with Web Services.
As an FYI, Powershell 7.0.0 LTS was released yesterday, which adds a handy switch to
Import-Module, theUseWindowsPowerShellswitch. This gives you he below when you use it:Module ReportingServicesTools is loaded in Windows PowerShell using WinPSCompatSession remoting session; please note that all input and output of commands from this module will be deserialized objects. If you want to load this module into PowerShell Core please use 'Import-Module -SkipEditionCheck' syntax
This means you can now use Windows Powershell Commands in Powershell (they've dropped the Core in the name now), and they're run in a compatible remote session. Given it a go with a few commands/modules that weren't working for me and seems to work well.
For those interested: What's New in PowerShell 7.0
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk -
Thanks for mentioning that Powershell 7 is out
- Phil Parkin wrote:Michael L John wrote:below86 wrote:
That's some bad code there Mike. I've seen some similar, but add a couple UNION statements and all with in an SSRS report. Talk about slow code.
I've also had that moment when I look at some code and say "Who wrote this crap?" Only to realize later it was me, about 10+ years ago. 😉
Gee, I look at code I wrote 2 days ago and wonder the same thing!
In a similar vein, if I look at any code I wrote more than about two weeks ago, I always wonder: "What is this trying to do and how the hell does it work?"
Well Phil, I really didn't want to admit to it, but what you said did happen to me this week. I wrote some code last month to do a complex calculation on each transaction record we received. Then I was looking back at it on Monday and thought How does this work? It's hell getting old. I guess some would say that is why you should put documentation in your code. The problem I usually run into is I write the code, look back at it at that time and think, "well that makes sense, no need for documentation". Hard to teach and old dog new tricks.
-------------------------------------------------------------
we travel not to escape life but for life not to escape us
Don't fear failure, fear regret. - MVDBA (Mike Vessey) wrote:Michael L John wrote:
I'm dealing with a crappy proc, and a crappy design, right now.
The devs did the "Code first" design. In other words, the ORM designed the database for them.
I can't post the code for the biggest offending proc, I don't feel like taking the time to obfuscate it. But, it does 16 selects into a temp table, of the same tables, with slightly differing WHERE clauses. it then selects distinct into another temp table, and then finally does a count and group by to get a count of each item.
There are 10 tables in this database. There are FORTY unused indexes in it. The devs keep trial and erroring adding indexes.
I could go on and on, but my fingers would get tired.
code first=don't care about database- someone elses problem
Heh... going for the 7th dwarf badge for "Acronyms"...
--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) -
you can't be 2 of the dwarfs at the same time
MVDBA
- below86 wrote:Phil Parkin wrote:Michael L John wrote:below86 wrote:
That's some bad code there Mike. I've seen some similar, but add a couple UNION statements and all with in an SSRS report. Talk about slow code.
I've also had that moment when I look at some code and say "Who wrote this crap?" Only to realize later it was me, about 10+ years ago. 😉
Gee, I look at code I wrote 2 days ago and wonder the same thing!
In a similar vein, if I look at any code I wrote more than about two weeks ago, I always wonder: "What is this trying to do and how the hell does it work?"
Well Phil, I really didn't want to admit to it, but what you said did happen to me this week. I wrote some code last month to do a complex calculation on each transaction record we received. Then I was looking back at it on Monday and thought How does this work? It's hell getting old. I guess some would say that is why you should put documentation in your code. The problem I usually run into is I write the code, look back at it at that time and think, "well that makes sense, no need for documentation". Hard to teach and old dog new tricks.
Old dog should find the most junior team member who has had nothing to do with it, and DON'T EXPLAIN IT TO THEM. Have them explain it to you after reviewing it for a few minutes. If they can't follow it, find out where they are stuck, comment appropriately.
-------------------------------------------------------------------------------------------------------------------------------------
Please follow Best Practices For Posting On Forums to receive quicker and higher quality responses - MVDBA (Mike Vessey) wrote:
you can't be 2 of the dwarfs at the same time
I bet Jeff owns an overcoat, that might work.
-------------------------------------------------------------------------------------------------------------------------------------
Please follow Best Practices For Posting On Forums to receive quicker and higher quality responses - MVDBA (Mike Vessey) wrote:
you can't be 2 of the dwarfs at the same time
BWAAA-HAAA!!!! Who said anything about "BE"? I'm knocking them off and hanging them on the fireplace. 😀
--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) - below86 wrote:Phil Parkin wrote:Michael L John wrote:below86 wrote:
That's some bad code there Mike. I've seen some similar, but add a couple UNION statements and all with in an SSRS report. Talk about slow code.
I've also had that moment when I look at some code and say "Who wrote this crap?" Only to realize later it was me, about 10+ years ago. 😉
Gee, I look at code I wrote 2 days ago and wonder the same thing!
In a similar vein, if I look at any code I wrote more than about two weeks ago, I always wonder: "What is this trying to do and how the hell does it work?"
Well Phil, I really didn't want to admit to it, but what you said did happen to me this week. I wrote some code last month to do a complex calculation on each transaction record we received. Then I was looking back at it on Monday and thought How does this work? It's hell getting old. I guess some would say that is why you should put documentation in your code. The problem I usually run into is I write the code, look back at it at that time and think, "well that makes sense, no need for documentation". Hard to teach and old dog new tricks.
A lot of people at work think that I write comments in code because of "standards". I'm old so I write comments in code for the very reason you've implied... massive CRS. 😀
--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) - jonathan.crawford wrote:MVDBA (Mike Vessey) wrote:
you can't be 2 of the dwarfs at the same time
I bet Jeff owns an overcoat, that might work.
Hmmmm.... hadn't thought of that. I normally wear one to hide the pork chop launcher I'm packin'. 😀
--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:below86 wrote:Phil Parkin wrote:Michael L John wrote:below86 wrote:
That's some bad code there Mike. I've seen some similar, but add a couple UNION statements and all with in an SSRS report. Talk about slow code.
I've also had that moment when I look at some code and say "Who wrote this crap?" Only to realize later it was me, about 10+ years ago. 😉
Gee, I look at code I wrote 2 days ago and wonder the same thing!
In a similar vein, if I look at any code I wrote more than about two weeks ago, I always wonder: "What is this trying to do and how the hell does it work?"
Well Phil, I really didn't want to admit to it, but what you said did happen to me this week. I wrote some code last month to do a complex calculation on each transaction record we received. Then I was looking back at it on Monday and thought How does this work? It's hell getting old. I guess some would say that is why you should put documentation in your code. The problem I usually run into is I write the code, look back at it at that time and think, "well that makes sense, no need for documentation". Hard to teach and old dog new tricks.
A lot of people at work think that I write comments in code because of "standards". I'm old so I write comments in code for the very reason you've implied... massive CRS. 😀
And the award for using of undefined acronyms goes to ...
- Lynn Pettis wrote:Jeff Moden wrote:
A lot of people at work think that I write comments in code because of "standards". I'm old so I write comments in code for the very reason you've implied... massive CRS. 😀
And the award for using of undefined acronyms goes to ...
He'd spell it out for you but he Can't Remember …..SQUIRREL!
-------------------------------------------------------------------------------------------------------------------------------------
Please follow Best Practices For Posting On Forums to receive quicker and higher quality responses
Viewing 15 posts - 64,561 through 64,575 (of 66,815 total)
You must be logged in to reply to this topic. Login to reply