Are the posted questions getting worse?
-
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
Worked with a survey software "few" years back, had soooo (texan style) many columns that when imported into SQL Server, it had to be vertically partitioned. Guess what, for a multiple choice survey those columns were all nvarchar(1).....still laughing:crazy:
😎
-
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
And then point at them and laugh some more?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events -
Ed Wagner (8/11/2015)
Sean Lange (8/11/2015)
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
I sort of get it when they allow NULL. I wouldn't design anything like that but I can understand where that comes from. But to allow variable length and force a single character just kills me. :-D:-D:-D
I especially love it when they use an NVARCHAR(1) to store a 0 or 1. Unfortunately, that's a real-life example.
It's not just an edge-case real life example either. I have seen something like this at just about every client I have had.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events -
SQLRNNR (8/11/2015)
Ed Wagner (8/11/2015)
Sean Lange (8/11/2015)
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
I sort of get it when they allow NULL. I wouldn't design anything like that but I can understand where that comes from. But to allow variable length and force a single character just kills me. :-D:-D:-D
I especially love it when they use an NVARCHAR(1) to store a 0 or 1. Unfortunately, that's a real-life example.
It's not just an edge-case real life example either. I have seen something like this at just about every client I have had.
Using SQL Server, storing a 0,1, or null; sounds like a good use of the BIT data type to me.
-
GilaMonster (8/11/2015)
And in unrelated news, something of moderate interest might be happening this afternoon/tonight (depending on timezones). Watch twitter.Is it this?
http://bit.ly/GailMastersBurnout
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events -
SQLRNNR (8/11/2015)
GilaMonster (8/11/2015)
And in unrelated news, something of moderate interest might be happening this afternoon/tonight (depending on timezones). Watch twitter.Is it this?
Yup.
Other than possible 24 Hours of PASS and PASS Summit feedback and some promised SQL University posts, the next blog post here will be a discussion of how not to go about doing a research degree while working full-time, which will be posted sometime after I get the thesis submitted.
And I did say "of moderate interest"
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
GilaMonster (8/11/2015)
SQLRNNR (8/11/2015)
GilaMonster (8/11/2015)
And in unrelated news, something of moderate interest might be happening this afternoon/tonight (depending on timezones). Watch twitter.Is it this?
Yup.
Other than possible 24 Hours of PASS and PASS Summit feedback and some promised SQL University posts, the next blog post here will be a discussion of how not to go about doing a research degree while working full-time, which will be posted sometime after I get the thesis submitted.
And I did say "of moderate interest"
Put the two together and does that mean we get to see blog content from you again? That is more than moderate interest. 😉
And the post was good. Not quite stern enough on the burnout topic - imho. Too many of us get too close to that edge.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events -
SQLRNNR (8/11/2015)
GilaMonster (8/11/2015)
SQLRNNR (8/11/2015)
GilaMonster (8/11/2015)
And in unrelated news, something of moderate interest might be happening this afternoon/tonight (depending on timezones). Watch twitter.Is it this?
Yup.
Other than possible 24 Hours of PASS and PASS Summit feedback and some promised SQL University posts, the next blog post here will be a discussion of how not to go about doing a research degree while working full-time, which will be posted sometime after I get the thesis submitted.
And I did say "of moderate interest"
Put the two together and does that mean we get to see blog content from you again? That is more than moderate interest. 😉
:Whistling:
And the post was good. Not quite stern enough on the burnout topic - imho. Too many of us get too close to that edge.
I wrote, rewrote and re-rewrote the last section for almost 2 months. It is still a little wishy-washy, I'm not entirely happy but I think it'll do as a starting point. It's a topic I'm probably going to come back to a few times, along with related observations, I may need a little more room than a blog post though.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
Ed Wagner (8/11/2015)
Sean Lange (8/11/2015)
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
I sort of get it when they allow NULL. I wouldn't design anything like that but I can understand where that comes from. But to allow variable length and force a single character just kills me. :-D:-D:-D
I especially love it when they use an NVARCHAR(1) to store a 0 or 1. Unfortunately, that's a real-life example.
Even better is when they use NVARCHAR(256). That was my first experience with blowing a pork chop bone out my nose.
--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 (8/11/2015)
Ed Wagner (8/11/2015)
Sean Lange (8/11/2015)
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
I sort of get it when they allow NULL. I wouldn't design anything like that but I can understand where that comes from. But to allow variable length and force a single character just kills me. :-D:-D:-D
I especially love it when they use an NVARCHAR(1) to store a 0 or 1. Unfortunately, that's a real-life example.
Even better is when they use NVARCHAR(256). That was my first experience with blowing a pork chop bone out my nose.
Do I smell Excel originated data here:ermm: Some of the worst legacy data I've worked with didn't even come in columns but few thousand characters streams of '0','1','N','D' and 'R', guess you know where this is going;-)
Packing this into ASN.1 just made my day
😎
-
SQLRNNR (8/11/2015)
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
And then point at them and laugh some more?
So you've read the HR reports?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore RooseveltAuthor of:
SQL Server Execution Plans
SQL Server Query Performance Tuning -
Grant Fritchey (8/11/2015)
SQLRNNR (8/11/2015)
Grant Fritchey (8/11/2015)
Sean Lange (8/11/2015)
OMG. I just ran across this in a database from a 3rd party. There are actually 50 nvarchar(1) columns with names 1 - 50. :w00t:ATTRIBUTE1 nvarchar(1)
ATTRIBUTE2 nvarchar(1)
.
.
.
ATTRIBUTE50 nvarchar(1)
VARCHAR(1) and NVARCHAR(1) are my absolute favorite "stupid database design" problems. Seriously. Love them. I point and laugh and laugh. Weird how the database design people don't appreciate the humor.
And then point at them and laugh some more?
So you've read the HR reports?
Makes for great comedy relief! 😛
-
Jeff Moden (8/11/2015)
Even better is when they use NVARCHAR(256). That was my first experience with blowing a pork chop bone out my nose.Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events -
Ed Wagner (8/11/2015)
Alvin Ramard (8/11/2015)
Ed Wagner (8/11/2015)
Sean Lange (8/11/2015)
Ed Wagner (8/11/2015)
The silver spoons need to be ordered again. Better get at least a case.Here's a quote I don't think I've every seen before:
Unfortunately I get your code to work.
http://www.sqlservercentral.com/Forums/Topic1709884-3077-2.aspx#bm1710535
I read that and I continually wonder why you and Lynn both continue to help this person. You guys put in way too much effort trying to help them and in return they put forth no effort, no learning and no details.
The whole quote from that is one of the more pathetic things I have seen. They got your code to work so they reverted to a simpler piece of code that doesn't work. :w00t:
Unfortunately I get your code to work.
Thank you for your script.
I reverted back to a simple script that is not really what I need.
I'm starting to wonder the same thing.
Would it be ok to suggest he have his boss contact me and I'll do it for a reasonable rate? Now he's asking for an Archive Delete Utility he can purchase.
Weak the force is. 🙁
I don't see why not. I've seen others do the same thing for other posts. Given the level of competence and sense of entitlement displayed thus far, however, I'd be cautious about investing a ton of time when you might not get paid.
BTW, I saw the most recent post, but I'm done.
I posted my suggested code. So far I got a thanks but no word as to whether or not he is using it or it works as he'd like.
-
SQLRNNR (8/11/2015)
Jeff Moden (8/11/2015)
Even better is when they use NVARCHAR(256). That was my first experience with blowing a pork chop bone out my nose.Can't place the movie or show that came from, but love the editing!
Viewing 15 posts - 50,056 through 50,070 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply