Viewing 15 posts - 30,181 through 30,195 (of 59,101 total)
michael vessey (5/4/2012)
capn.hector (5/4/2012)
Eugene Elutin (5/4/2012)
Jeff Moden (5/3/2012)
michael vessey (5/2/2012)
does the following count as a loop?INSERT INTO dbo.yourTable default values
go 100
??:-P??
BWAAAA-HAAAA!!!!! Ask that question on the receiving end of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2012 at 1:19 pm
Ummmm... I've not run any of the code but, just by looking, shouldn't any ordering be done in descending order so that you get the "latest" row like what the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2012 at 8:07 am
W. Kevin Hazzard (5/4/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 4, 2012 at 7:55 am
You can use ROW_NUMBER() OVER for this.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 8:20 pm
opc.three (5/3/2012)
Lowell (5/3/2012)
I made a suite of CLR export functions as a proof of concept, and i can export to any text data type or...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 7:55 pm
michael vessey (5/2/2012)
does the following count as a loop?INSERT INTO dbo.yourTable default values
go 100
??:-P??
BWAAAA-HAAAA!!!!! Ask that question on the receiving end of an interview and see what happens. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 7:19 pm
NLV (5/2/2012)
Hi,I want to insert 100 rows like (1,2,3,4,..100) without using loops into a table using CTE. can you please help.
Ok... getting back on track for this thread... I've got...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 7:14 pm
Using the data you provided, this will produce the correct output. I'll leave it up to you to format the dates.
WITH
cteEnumerate AS
( --=== Assign a numeric sequence to each...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 6:45 pm
imarran (5/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 6:04 pm
W. Kevin Hazzard (5/3/2012)
CREATE PROCEDURE [dbo].[usp_Employee_Select_Down_Param_EmpID]
@selectEmpID INT = NULL, -- NULL = all
@maxSupLevel...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 5:53 pm
polkadot (5/3/2012)
Do we have to convert datetime to varchar (Jeff, ColdCoffee)?
If we don't is it *better not to* (you guys)?
What is internationally sensitive...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 5:38 pm
drew.allen (5/2/2012)
I simply see no advantage and...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 11:02 am
There is indeed. But I'd like to see what you think you'd like the output to look like.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 7:22 am
hayden-508426 (5/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 6:57 am
imarran (5/3/2012)
yes, I have done this often with rCTE's which is much faster 🙂
Proof!!! Let's see the proof for your claim!!!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 3, 2012 at 6:51 am
Viewing 15 posts - 30,181 through 30,195 (of 59,101 total)