I'm using your same code but I don't get an error.

CREATE TABLE tblHoliday( HolidayDate date);

INSERT INTO tblHoliday

VALUES('20150101'),

('20150425');

CREATE TABLE tblPeriod( StartDate date, EndDate date);

INSERT...

What about inserting it into a global temp table? Would that cause issues?

You can't use GO inside a dynamic sql statement. GO isn't a T-SQL keyword, it's a batch generator interpreted by SSMS.

Or maybe you might need a LIKE in your JOIN clause.

SELECT

TB.DiaryID

,TA.MedicalCodeID

FROM dbo.TableA TA

JOIN dbo.TableB TB ON TB.EmisCode LIKE TA.EmisCode + '%';

Does this help?

http://answers.microsoft.com/en-us/windows/forum/windows_7-pictures/error-the-application-has-failed-to-start-because/df019c0d-746e-42d0-ad68-465e18e3f3ef

No, it's not possible.

From BOL.

This is an awful query, but it's not just the query. The problem comes from the database design. I see a special problem on dbo.avoice_vw_TableDetail as it is completely denormalized.

Another...

As previously stated, you need to normalize your table. If you can't change the schema, you still need to code the normalization and denormalize again. Here's a sample on how...

Anshul Parmar (4/1/2015)

---

If you don't have a calendar table or if you don't want to use a calendar table. Use CTE instead-

;WITH CTE AS

(

SELECT CAST('2015-03-01' AS...

What's the error? What are you trying to do?

As previously said, you can use a cross apply.

I'm leaving both options. Note that the join needs to calculate all the values before joining and that's why it can be...

I had the same question some days ago and only found that the index creation affected the column modify_date in sys.objects. If the index supports a constraint, you could query...

Maybe something here or here could help you.

Why are you concatenating the date with itself? What are you trying to do?

There's no problem concatenating dates if you use CONVERT()

DECLARE @SampleData TABLE(

SomeDate date)

INSERT INTO...

Maybe you could do this to find offending rows.

select fieldname

from tablename

EXCEPT

select fieldname

from tablename

where fieldname

NOT LIKE N'%[^'+nchar(0x9)+nchar(0xA)+nchar(0xD)+nchar(0x20)+N'-'+nchar(0xD7FF)+N']%'

The NOT LIKE N'%[^Pattern]%' will return non-offending rows....