and your question is?

Anju Renjith (3/23/2015)

---

Thanks for all the responses..

I get the data from 3 different tables. I used case when to get the result as needed. It works fine...

As Chris in the above post suggested that you will get much quicker response if you supply with create table code too.

Here is the code, which I have done, as...

I use SVN Tortoise for a source control.

Just to let you know that the image is not showing here on the thread.

i am reading up on gaps and islands itzik ben gan too now..path to self eductaion or self destruction. 😛

TheSQLGuru (3/18/2015)

---

Do a web search gaps and islands itzik ben gan....

superb!!!Thanks a lot sir 🙂 🙂 🙂

Final code:

WITH cte AS

(

SELECTTestId,

TestDate,

--[GroupBy] = TestDate - rn,

RANK() OVER (

PARTITION BYTestId

ORDER BYTestDate - rn

)AS OrderId

FROM(

SELECTTestId,

TestDate,

ROW_NUMBER() OVER

(

PARTITION BY TestId

ORDER BY TestDate

)AS...

Output:

TestId TestDate rn ...

yup...it is showing up now

lesson learnt: "Patience is a virtue"

I managed to calculate difference between second and previous row:

SELECTTestId,

TestDate,

DIFF

FROM(

SELECTa.*,

b.TestDate AS PreviousRecordDate,

CASE WHEN DATEDIFF(DAY, b.TestDate, a.TestDate) <=1 THEN 0 ELSE 1 END AS DIFF

FROMdbo.tblDatesSequenceTest AS a

LEFT OUTER JOINdbo.tblDatesSequenceTest AS b

ONa.TestId=b.TestIdAND

a.TestDate=b.TestDate...

select * from mytable

where class='something'

and ISNULL(xyz, 99) = 1);

it can be sorted by keeping the required column in a view.

You could put all the sheet names in a system table and pick up all the names one by one from there, in a WHILE loop.

I have a very simple script which imports multiple excel files into a SQl table:

USE [Landcatch]

DECLARE @archivePath VARCHAR(500), @templateFolder VARCHAR(100), @cmd NVARCHAR(4000);

SELECT @archivePath = 'C:\', -- Excel file path comes...

The link: http://sqldigger.bdsweb.be to download the SQL Digger is not working, is there any other link where it can be downloaded from?

Hi Darren,

You might already have tried this but other way to tracking error is by doing:

PRINT @sDosCommand

before executing the command and see if there are any obvious typos or syntax...