Viewing 15 posts - 16,861 through 16,875 (of 59,101 total)
patilpallavi16 (9/13/2016)
declare @naiccode int = 12345
SELECT Policy.policyType, Policy.policyNum, Policy.effectiveDate, '12345' AS "NAIC Code" ,
Insured.lname1, Insured.middle1,
Insured.fname1, Insured.address1, Insured.city, Insured.state, Insured.zip FROM Policy FULL JOIN
Insured ON...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 6:47 pm
Hugo Kornelis (9/12/2016)
What I should have written was "a WHILE loop, no matter how well written it is, will never ever beat a (well written) cursor".
Do you have some readily...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 6:33 pm
From the Article:
An organization wouldn't need to cater food every night.
Night? Free brainstorming for the company and it's at night?
I've heard of "Down Tools" or "Down Weeks" before but there's...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 5:56 pm
That is unless the temp table starts with two "#" signs, which makes it a "Global Temp Table", and then the answer would be "yes".
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 5:29 pm
amy26 (9/14/2016)
Thank you so much! Perfect!
Curiosity question please. Which method did you use?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 5:18 pm
Eirikur Eiriksson (9/14/2016)
Jeff Moden (9/14/2016)
Eirikur Eiriksson (9/13/2016)
First few rows of the output (wich obviously will not be the same again)
Not guaranteed to be true, though. Because of the translations,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 5:17 pm
sqlenthu 89358 (9/14/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 5:14 pm
The nest questions would be.... do you have anything in the database that you couldn't easily recreate and are you backing up the database on a very regular basis.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 4:38 pm
Best way to fix this is to have a pork chop dinner with the people that are providing the data. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 4:33 pm
dallas13 (9/14/2016)
Jeff- I understand your concern but we have data coming from third party so we have to massage data here.
The Dixie Flatline- You are right....
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 12:03 pm
dallas13 (9/14/2016)
CREATE TABLE #UnPivotExample(code varchar(2), value int)
INSERT INTO #UnPivotExample (code,value)
SELECT code,value
FROM
(SELECT [AZ], [NY], [PA] FROM #Example
) AS cp
UNPIVOT
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 9:46 am
Eirikur Eiriksson (9/13/2016)
First few rows of the output (wich obviously will not be the same again)
Not guaranteed to be true, though. Because of the translations, as unlikely as it...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 7:42 am
Jason A. Long (9/13/2016)
IF OBJECT_ID('tempdb..#Example','U') IS NOT NULL
DROP TABLE #Example;
CREATE TABLE #Example (
id INT,
AZ INT NULL,
NY INT NULL,
PA INT NULL
);
GO
INSERT#Example (id,AZ,NY,PA) VALUES (1, '5','7','5'),(2, '2','3','5'),(3, '3','2','5');
SELECT
e.id,
x.State,
x.Value
FROM
#Example e
CROSS...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2016 at 12:10 am
Thanks, Steve. I really appreciate the time you took to explain that. You folks definitely put some thought into that.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2016 at 11:25 pm
amy26 (9/13/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
September 13, 2016 at 12:53 pm
Viewing 15 posts - 16,861 through 16,875 (of 59,101 total)