|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Yesterday @ 1:00 PM
Points: 3,459,
Visits: 2,535
|
|
| This is a good one - ending the week on a high note. Thanks, Kenneth!
|
|
|
|
|
SSChampion
        
Group: General Forum Members
Last Login: Today @ 1:49 AM
Points: 10,990,
Visits: 10,540
|
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 5:30 AM
Points: 861,
Visits: 1,436
|
|
Richard Warr (9/7/2012)
I looked at the first option and was disappointed that the second one wasn't Collect $200 for parsing GO.

Loved the question BTW. No catch, just expected behavior.
Best regards,
Andre Guerreiro Neto
Database Analyst http://www.softplan.com.br MCITPx1/MCTSx2
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 6:48 AM
Points: 533,
Visits: 260
|
|
| good question, caught me out!
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Friday, March 22, 2013 5:58 PM
Points: 561,
Visits: 440
|
|
The benefit of replying a few days later and fully caffeinated. :D
Even so, I almost missed the INSERT ... SELECT part. 
Fun question, and yes, a helpful technique for populating tables with large amounts of test data.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: 2 days ago @ 7:36 AM
Points: 245,
Visits: 148
|
|
Damn! Got the go part right, but didn't read the select closely enough. But good to remember this way to create an exponentially rising number of records in a hurry.
Thank you for the question.
|
|
|
|
|
Say Hey Kid
      
Group: General Forum Members
Last Login: Monday, February 18, 2013 6:17 AM
Points: 674,
Visits: 472
|
|
Great question thanks.
"Be brave. Take risks. Nothing can substitute experience."
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: 2 days ago @ 8:48 AM
Points: 2,440,
Visits: 714
|
|
Nice that you can't "GO" in a T-SQL statement. What a nightmare that would be for anyone trying to avoid SQL Injection issues.
Jamie
|
|
|
|