Because you have the table alias in the wrong place:

select t.cbclaim from [dev].[stage].[dbo].[claimsview] t with(noexpand)

Sean Lange (5/9/2013)

---

Lynn Pettis (5/9/2013)

---

You may be right...

Care to give a more in depth explainatioin? I'm lost as to the questioin.

jagat.patel (5/9/2013)

---

Thanks

ddl looks good

O/P i am looks at is all dates when flag changes it's value

so in case of

id = 1 dates are

3/1/2013 and 4/1/2013

and for id 2 date...

Sean Lange (5/9/2013)

---

TeraByteMe (5/9/2013)

---

And below are the rest of the questions. BTW, I took myself out of being considered for candidacy for the role so I am not be considered...

Run against your shadow copy, not production:

DBCC CHECKDB database_name WITH ALL_ERRORMSGS, NO_INFOMSGS

If it returns errors, post all of it (you can put it in a text file and attach...

Don't do it just for us, do it for yourself. Well formatted code is actually easier to...

Eugene Elutin (5/9/2013)

---

Lynn Pettis (5/9/2013)

---

Eugene Elutin (5/9/2013)

---

Lynn Pettis (5/8/2013)

---

Eugene Elutin (5/8/2013)

---

Actually you can, if you really want or need to!

You should use cursor datatype in output parameter of your procedure....

anuj12paritosh (5/9/2013)

---

Hi jhon,

Actually my problem is something different ,if you have any solution so please see problem and provide exact solution above provide query is not a solution pls check...

Sorry, there is no sys.processes. The system table sysprocessess mappes to the following:

sys.dm_exec_connections

sys.dm_exec_sessions

sys.dm_exec_requests

There is no binary conversion style in SQL Server 2005. This was added in SQL Server 2008.

You say you are using SQL Server 2008 R2. What version of SQL Server are you connected to when you run these?

Run the following:

DECLARE @VARBINARY VARBINARY (16)

SET @VARBINARY =...

Post your code, even if it is identical.

Hard to answer with the vague information you have provided.

First, what makes up your fiscal periods (months, quarters, year)?

Second, since we can't see what you see there really isn't anything...

When I run the following in SQL Server 2008 R2:

DECLARE @VARBINARY VARBINARY (16)

SET @VARBINARY = CONVERT(VARBINARY (16),'0x0000000000018662',1)

SELECT @VARBINARY;

go

DECLARE @VARBINARY VARBINARY (16)

SET @VARBINARY = CONVERT(VARBINARY (16),'0x0000000000018662',0)

SELECT @VARBINARY;

go

I get;

0x0000000000018662

0x30783030303030303030303030313836