The length part of your recommendation here has not bearing; varchar is actually longer.

That said nvarchar is not a bad idea to avoid the conversion. The convert is very low...

REALLY??? WOW.. I have written a fair amount in the past however this is by far the largest dynamic project I have worked and in effect reverse engineers the relationship...

No I am not sure I following what you are suggesting here or I am missing the point.

So I build a dynamic query. In this case it is TWO joins...

Not exactly.

The execution comes later in another proc.

HOWEVER the printing of the variable is just BEFORE I set the variable value to the DB. What is printed to screen is...

Oh I got rid of that, sorry. All I did was make another table with just two fields ETLMappingID and PreparedStatement varchar(max)

Then in the PROC added another block UPDATE...

Table DDL:

USE [ETL]

GO

/****** Object: Table [dbo].[ETLPreparedStatement] Script Date: 4/28/2016 12:00:28 PM ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING ON

GO

CREATE TABLE [dbo].[ETLPreparedStatement](

[PreparedStatementID] [int] IDENTITY(1,1) NOT NULL,

[ETLMappingID] [int] NOT...

PROC:

USE [ETL]

GO

/****** Object: StoredProcedure [dbo].[ETLProcessTableFieldsDynamic_JOIN2] Script Date: 4/28/2016 11:13:55 AM ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

ALTER PROCEDURE [dbo].[ETLProcessTableFieldsDynamic_JOIN] (@BatchID int)

AS

--EXEC ETLProcessTableFieldsDynamic_JOIN 4045

...

This is just crazy.

Below is the proc and the table DDL (Which I posted earlier).

When I run the proc my PRINT statement throws this on screen. I am printing the...

Wow.. That is a reach?? But what the heck why not, I obviously don't have the answer.

I know it is something with a server setting or something, not code.

Made another table varchar(8000)

I inserted few hundred characters then just did update where field = field + field.

When...

I will check settings but I don't think that his it.

See when the stored procedure runs I have print statements that will show on screen what my built string is....

Thank you but no triggers, no functions being called. I am the only developer on this and this is a standalone table.

I have not only done a query for the...

In the Print statements when the proc runs; everything is fine.

The problem comes in updating the table, I am limited to 4000 characters for some reason.

If I come up with...

Here you are:

USE [ETL]

GO

/****** Object: Table [dbo].[ETLPreparedStatement] Script Date: 4/27/2016 2:32:23 PM ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING ON

GO

CREATE TABLE [dbo].[ETLPreparedStatement](

[PreparedStatementID] [int] IDENTITY(1,1) NOT NULL,

[ETLMappingID] [int]...

The LEN when saved to table is 4k.