Viewing 15 posts - 24,916 through 24,930 (of 59,102 total)
jimgawn (1/2/2014)
No we don't. That's a Luddite position. T-SQL has a fairly rich set of string-manipulation...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 8:55 am
That would be the exact reason for reading the column header into a table and doing the comparison. It would show the basic structure to the user and identify...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 8:31 am
Excellent. Thanks for the feedback.
On the Oracle shift that you're having to make (I had to work with Oracle for about 3 years), my best advice would be to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 8:28 am
ChrisM@Work (1/3/2014)
Jeff Moden (1/2/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 8:25 am
Thanks for stopping by, Erik.
From what I understand, the SEQUENCEs of 2012 aren't the same as the "Generate_Series" functionality of PostGre. SEQUENCEs still rely on rows being present where...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 8:18 am
prakashr.r7 (1/3/2014)
Jeff Moden (1/2/2014)
prakashr.r7 (1/2/2014)
Why are we not able to rebuild indexes having BLOB data? do we need to drop and recreate in alternate?
You can rebuild indexes that contain BLOB...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 8:11 am
I missed this article the first time around. Nice job, Geoff.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 12:58 am
sneumersky (1/2/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2014 at 12:06 am
Scott Abrants (1/2/2014)
Outstanding article, nicely done with great examples.
I am certain this misuse is rampant in the real world and your examples help clarify where to look for these...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2014 at 11:25 pm
wolfkillj (1/2/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2014 at 10:19 pm
PHYData DBA (1/2/2014)
Jeff Moden (1/9/2011)
Mike McIver (1/9/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2014 at 9:56 pm
So read the first row (the header row) into a table and do a comparison.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2014 at 4:24 pm
Emptymoon (1/2/2014)
Done.
Please share. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2014 at 4:11 pm
You can also just create a view called (for example) ANewID that generates a GUID as a single column, single row result and simply join to it as a CROSS...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2014 at 4:03 pm
Use TAB delimiters, instead?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2014 at 3:10 pm
Viewing 15 posts - 24,916 through 24,930 (of 59,102 total)