Viewing 15 posts - 23,986 through 24,000 (of 59,099 total)
Just a small simplification of Luis' fine code...
WITH SampleData AS(
SELECT 55 Value UNION ALL
SELECT 63 UNION ALL
SELECT 26
)
SELECT Value,
SIGN(Value & 64) AS Sat,
SIGN(Value & 32) AS Fri,
SIGN(Value & 16) AS...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 10:29 pm
Such code is a little out of my league but I don't see where you're drilling down past the main folder at all.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 10:07 pm
I guess that pretty much puts the cap on the rumor that the cloud was going to kill the position of "DBA" in all it's wonderous mryiad of forms. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 10:03 pm
TheSQLGuru (4/2/2014)
I don't see it listed here though, just the outer joins: http://technet.microsoft.com/en-us/library/bb510662.aspx
or here (although there are some rather surprising things supposedly being REMOVED in SQL 2014 and future...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 9:55 pm
I sure do appreciate the positive feedback. Glad it's working for you.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 9:48 pm
Ok... first things first. This method needs a good, high performance string splitter. You can find a really good one in the article at the following link in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 9:18 pm
Thanks for the feedback. What did your final code end up looking like? I ask only because I want to make sure that it won't be a problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 7:21 pm
milos.radivojevic (4/2/2014)
Since the ALTER TABLE statement is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 5:17 pm
vanessa4biz (4/2/2014)
I agree with you hundred percent but this is a legacy system and management is afraid to change the data type in fear that it may cause other problems.
Understood....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 5:00 pm
drew.georgopulos (4/2/2014)
I found this http://www.sqlperformance.com/2012/07/t-sql-queries/split-strings
which was great summation of the blizzard of solutions I found here, which was kind of an embarrassment of riches :-P.
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 4:55 pm
george sibbald (4/2/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 4:14 pm
ScottPletcher (4/2/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 4:01 pm
Sean Lange (4/2/2014)
vanessa4biz (4/2/2014)
ALTER TABLE dbo.tablename
ADD CONSTRAINT DF_Date_format
check (SDate LIKE '%[1-2][0-9][0-9][0-9]/[0-1][0-9]/[0-3][0-9]%')
******But this does not work for VARCHAR data type...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 3:56 pm
Hugo Kornelis (4/2/2014)
The UPDATE ... FROM used in the trigger is a highly dangerous construction that, if I had my way, would have been deprecated a long time ago already.
I'm...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 3:16 pm
Carlo Romagnano (4/2/2014)
In sqlserver 2008 r2 the update doesn't return any resultset and no error message.(2 row(s) affected)
(2 row(s) affected)
What I'm missing?
Same here.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 2, 2014 at 3:12 pm
Viewing 15 posts - 23,986 through 24,000 (of 59,099 total)