Quick thought, use the LIKE operator

😎

USE tempdb;

GO

DECLARE @test-2 TABLE

(

TEST_ID INT IDENTITY(1,1) NOT NULL PRIMARY KEY CLUSTERED

,TEST_STRING VARCHAR(50) ...

Quick question, are you using tabular SSAS/dax?

😎

bhavik.bk (8/21/2014)

---

G'day

was reading Distinct function on technet. There is a bit about VALUES FUNCTION. Anyone has idea how to use it? I tried using like distinct for a column,but...

Quick though, first move towards an SQL set based solution is to change the word Loop to Group. Each Group starts with Coke/Fanta and ends in a HardDrink:doze:

😎

Here is an...

After the second coffee I realised that the solution was in fact "current row and X following", here is a "X preceding and current row" improvement.

😎

use master

go

set nocount on

go

/**********************

** BUILD...

Here is a little "first coffee in the morning" solution:doze:

It uses two instances of a Tally CTE to generate a set N{N+0,,,,N+x} for framing the x rows preceding and current...

Edit: Oops, thought I was replying to this thread :w00t:

You are spot on, now I can reply which I could not do before your second post.:-)

😎

Here is a quick suggestion, should result in more consistent plan (for better or worse)

😎

CREATE PROCEDURE [Quotation].[Get_Quotes_LH] ( @From DateTime = null, @To DateTime = null )

AS

BEGIN

...

Quick thought, to find the conversion causing the error, get the execution plan XML and look for an implicit cast to datetime. Also any value higher than 2958463 (9999-12-31) will...

First noticed this yesterday, also sometimes the format changes, could be a separate CSS issue though.

Kind of annoying, spent about an hour writing an answer and then I couldn't...

Lynn Pettis (8/21/2014)

---

Eirikur Eiriksson (8/21/2014)

---

Lynn Pettis (8/21/2014)

---

It...

Lynn Pettis (8/21/2014)

---

It may be but it...

Quick note, INFORMATION_SCHEMA is an ANSI compliant metadata view collection added in 2000 if I remember correctly, sys.* is SQL Server specific.

😎

Make certain that the SQL Server 2008 R2 SSIS components are installed on the server, normally found under C:\Program Files (x86)\Microsoft SQL Server\100\DTS

😎

Quick thought, have you tried using WITH RECOMPILE?

😎

In addition, are the statistics up to date?