Viewing 15 posts - 19,096 through 19,110 (of 59,072 total)
o324712 (11/22/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 22, 2015 at 9:17 am
homebrew01 (11/21/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 5:33 pm
tripleAxe (11/18/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 5:12 pm
jmpatchak (11/20/2015)
This does a really great job of generating random test data. What I'm looking for is a query that pulls out the data from the Battle table that...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 5:05 pm
Ed Wagner (11/21/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 4:36 pm
Steve Jones - SSC Editor (11/21/2015)
you guys are killing me with questions and not t-sql problems. :w00t:
That's because T-SQL isn't a problem. 😛
I think we need to get a couple...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 3:54 pm
omegadev21 (11/21/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 2:55 pm
Steve Jones - SSC Editor (11/21/2015)
Jeff Moden (11/19/2015)
Steve Jones - SSC Editor (11/19/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 2:53 pm
Ok... caught a break from work.
Here's a two row test table. This is NOT a part of the solution. It's just a test table to show the possibilities....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 1:55 pm
omegadev21 (11/20/2015)
Alan.B (11/20/2015)
omegadev21 (11/20/2015)
Jeff Moden (11/20/2015)
Ah... maybe I missed it. Is this the data example?
Given the field CLIENT_DATA of data type VARCHAR(MAX) with data:{"LASTNAME":"Doe","FIRSTNAME":"John","EMAILADDRESS":"something@email.com","USERNAME":"exusername","PHONENUMBER":"15555555555"}
@jeff Moden, yeah that's the sample...
If...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 21, 2015 at 5:57 am
Ah... maybe I missed it. Is this the data example?
Given the field CLIENT_DATA of data type VARCHAR(MAX) with data:
{"LASTNAME":"Doe","FIRSTNAME":"John","EMAILADDRESS":"something@email.com","USERNAME":"exusername","PHONENUMBER":"15555555555"}
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2015 at 9:51 pm
omegadev21 (11/20/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2015 at 9:45 pm
I have a far better idea...
Drive to the building where the person who sent you the hierarchical, denormalized crap and beat the hell out of them for being so stupid....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2015 at 9:28 pm
RVO (11/20/2015)
I inherited this ETL process from guys who designed it 2 years ago.It will be replaced by JAVA solution in 2016.
It'll be interesting to see how that works out....
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2015 at 3:00 pm
I learned NOT to be an early adopter of anything long before I started working with SQL Server. After seeing things like 2000 SP3, 2005 RTM, 2008, 2012 RTM,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 20, 2015 at 2:51 pm
Viewing 15 posts - 19,096 through 19,110 (of 59,072 total)