Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««4,0604,0614,0624,0634,064»»»

Are the posted questions getting worse? Expand / Collapse
Author
Message
Posted Thursday, July 18, 2013 12:01 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 9:11 AM
Points: 7,128, Visits: 6,291
dwain.c (7/17/2013)
Brandie Tarvin (7/17/2013)
WHOO HOO!

Not only did I just teach myself how to use MERGE (never had time or reason), but I managed to use it correctly with a Cross Applied Tally table and an INNER JOIN inside the USING clause.

<SnoopyDance>

And it only took me 30 minutes to figure it all out.


One thing to take care with when using MERGE though: A Hazard of Using the SQL Merge Statement

It's not a bug it's a feature, but does have the potential to cause you grief if you don't know about it.


Okay. Read the article. Reread it again. I understand the conclusion, but the content was a little iffy. There are certain assumptions made about the reader understanding what the writer was doing without setting up a plain English business case. So I'm still confused on why the author decided to deliberate throw in a DELETE on the NOT MATCHED BY SOURCE bit and then act surprised when it worked as advertised.

Thanks for the link, though.


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1475161
Posted Thursday, July 18, 2013 2:44 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 2:49 PM
Points: 13,069, Visits: 11,908
Is the email queue backed up again? I haven't received notifications all day today. Anybody else?

_______________________________________________________________

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 Moden's splitter.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Understanding and Using APPLY (Part 1)
Understanding and Using APPLY (Part 2)
Post #1475222
Posted Thursday, July 18, 2013 3:34 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:50 PM
Points: 5,974, Visits: 12,877
Sean Lange (7/18/2013)
Is the email queue backed up again? I haven't received notifications all day today. Anybody else?


me neither


---------------------------------------------------------------------

Post #1475231
Posted Thursday, July 18, 2013 7:16 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 6:01 PM
Points: 3,609, Visits: 5,222
Brandie Tarvin (7/18/2013)
dwain.c (7/17/2013)
Brandie Tarvin (7/17/2013)
WHOO HOO!

Not only did I just teach myself how to use MERGE (never had time or reason), but I managed to use it correctly with a Cross Applied Tally table and an INNER JOIN inside the USING clause.

<SnoopyDance>

And it only took me 30 minutes to figure it all out.


One thing to take care with when using MERGE though: A Hazard of Using the SQL Merge Statement

It's not a bug it's a feature, but does have the potential to cause you grief if you don't know about it.


Okay. Read the article. Reread it again. I understand the conclusion, but the content was a little iffy. There are certain assumptions made about the reader understanding what the writer was doing without setting up a plain English business case. So I'm still confused on why the author decided to deliberate throw in a DELETE on the NOT MATCHED BY SOURCE bit and then act surprised when it worked as advertised.

Thanks for the link, though.


I agree. That author's an amateur. But it was fun to write.



My mantra: No loops! No CURSORs! No RBAR! Hoo-uh!

My thought question: Have you ever been told that your query runs too fast?

My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.


Need to UNPIVOT? Why not CROSS APPLY VALUES instead?
Since random numbers are too important to be left to chance, let's generate some!
Learn to understand recursive CTEs by example.
Splitting strings based on patterns can be fast!
Post #1475245
Posted Friday, July 19, 2013 12:26 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Sunday, July 20, 2014 11:20 PM
Points: 13,252, Visits: 10,133
dwain.c (7/18/2013)
Brandie Tarvin (7/18/2013)
dwain.c (7/17/2013)
Brandie Tarvin (7/17/2013)
WHOO HOO!

Not only did I just teach myself how to use MERGE (never had time or reason), but I managed to use it correctly with a Cross Applied Tally table and an INNER JOIN inside the USING clause.

<SnoopyDance>

And it only took me 30 minutes to figure it all out.


One thing to take care with when using MERGE though: A Hazard of Using the SQL Merge Statement

It's not a bug it's a feature, but does have the potential to cause you grief if you don't know about it.


Okay. Read the article. Reread it again. I understand the conclusion, but the content was a little iffy. There are certain assumptions made about the reader understanding what the writer was doing without setting up a plain English business case. So I'm still confused on why the author decided to deliberate throw in a DELETE on the NOT MATCHED BY SOURCE bit and then act surprised when it worked as advertised.

Thanks for the link, though.


I agree. That author's an amateur. But it was fun to write.


Ouch.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1475280
Posted Friday, July 19, 2013 5:06 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 9:11 AM
Points: 7,128, Visits: 6,291
dwain.c (7/18/2013)
Brandie Tarvin (7/18/2013)
dwain.c (7/17/2013)
Brandie Tarvin (7/17/2013)
WHOO HOO!

Not only did I just teach myself how to use MERGE (never had time or reason), but I managed to use it correctly with a Cross Applied Tally table and an INNER JOIN inside the USING clause.

<SnoopyDance>

And it only took me 30 minutes to figure it all out.


One thing to take care with when using MERGE though: A Hazard of Using the SQL Merge Statement

It's not a bug it's a feature, but does have the potential to cause you grief if you don't know about it.


Okay. Read the article. Reread it again. I understand the conclusion, but the content was a little iffy. There are certain assumptions made about the reader understanding what the writer was doing without setting up a plain English business case. So I'm still confused on why the author decided to deliberate throw in a DELETE on the NOT MATCHED BY SOURCE bit and then act surprised when it worked as advertised.

Thanks for the link, though.


I agree. That author's an amateur. But it was fun to write.


Did not read the author's name when I read the article. Sorry. Didn't realize it was you.


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1475376
Posted Friday, July 19, 2013 6:16 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 9:10 AM
Points: 1,211, Visits: 6,541
Brandie Tarvin (7/19/2013)
dwain.c (7/18/2013)
Brandie Tarvin (7/18/2013)
dwain.c (7/17/2013)
Brandie Tarvin (7/17/2013)
WHOO HOO!

Not only did I just teach myself how to use MERGE (never had time or reason), but I managed to use it correctly with a Cross Applied Tally table and an INNER JOIN inside the USING clause.

<SnoopyDance>

And it only took me 30 minutes to figure it all out.


One thing to take care with when using MERGE though: A Hazard of Using the SQL Merge Statement

It's not a bug it's a feature, but does have the potential to cause you grief if you don't know about it.


Okay. Read the article. Reread it again. I understand the conclusion, but the content was a little iffy. There are certain assumptions made about the reader understanding what the writer was doing without setting up a plain English business case. So I'm still confused on why the author decided to deliberate throw in a DELETE on the NOT MATCHED BY SOURCE bit and then act surprised when it worked as advertised.

Thanks for the link, though.


I agree. That author's an amateur. But it was fun to write.


Did not read the author's name when I read the article. Sorry. Didn't realize it was you.


I had the same thoughts, but made the connection of who the author was.
Good constructive comment, outline a business case to set up the article better.
Post #1475424
Posted Friday, July 19, 2013 8:05 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 12:12 PM
Points: 15,517, Visits: 27,896
I was doing some research this morning and got sucked down a rabbit hole (it happens) and landed on a series of sites complaining about Stack Overflow and Stack Exchange. This one, mainly the comments, really struck me:http://sergworks.wordpress.com/2012/09/26/why-stackoverflow-sucks/

I think we were heading down that path a little, but it seems like we self-corrected. Just wanted to say thanks to all the Threadizens for not turning us into something bad.

PS: I even did a series of searches in Gingle for "'sql server central' sucks" and variations on that theme and just couldn't find anything too bad. Either we're invisible (unlikely) or we done good. Pat yourselves on the back.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1475502
Posted Friday, July 19, 2013 8:23 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 2:49 PM
Points: 13,069, Visits: 11,908
Grant Fritchey (7/19/2013)
I was doing some research this morning and got sucked down a rabbit hole (it happens) and landed on a series of sites complaining about Stack Overflow and Stack Exchange. This one, mainly the comments, really struck me:http://sergworks.wordpress.com/2012/09/26/why-stackoverflow-sucks/

I think we were heading down that path a little, but it seems like we self-corrected. Just wanted to say thanks to all the Threadizens for not turning us into something bad.

PS: I even did a series of searches in Gingle for "'sql server central' sucks" and variations on that theme and just couldn't find anything too bad. Either we're invisible (unlikely) or we done good. Pat yourselves on the back.


We have from time to time started heading in a bad direction. The good news is that there always seems to be a few people around here who remind us or nudge us back to the "good side". I am pretty sure that most of the "regulars" around here have been on both sides of that nudging once or twice.

I think that by not having those idiotic reputation points we have served ourselves and our community well in the long run. To be honest, a down vote is quite rude. Many times it is somebody who is honestly trying to help but posts a less then optimal solution. At least around here we tend to educate not only the OP but also the responder in those cases. The lack of reputation points I think eliminates some of the BS favorites type of crap. We can stick to what is important, the question and not stroking our egos.



_______________________________________________________________

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 Moden's splitter.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Understanding and Using APPLY (Part 1)
Understanding and Using APPLY (Part 2)
Post #1475512
Posted Friday, July 19, 2013 8:46 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 12:12 PM
Points: 15,517, Visits: 27,896
Sean Lange (7/19/2013)

We have from time to time started heading in a bad direction. The good news is that there always seems to be a few people around here who remind us or nudge us back to the "good side". I am pretty sure that most of the "regulars" around here have been on both sides of that nudging once or twice.

I think that by not having those idiotic reputation points we have served ourselves and our community well in the long run. To be honest, a down vote is quite rude. Many times it is somebody who is honestly trying to help but posts a less then optimal solution. At least around here we tend to educate not only the OP but also the responder in those cases. The lack of reputation points I think eliminates some of the BS favorites type of crap. We can stick to what is important, the question and not stroking our egos.



What's that?

I can't hear you since you have less than 10,000 points.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1475526
« Prev Topic | Next Topic »

Add to briefcase «««4,0604,0614,0624,0634,064»»»

Permissions Expand / Collapse