Hello and welcome to the forum. As your question relates to spreadsheets (Google Sheets?) rather than SQL Server, which is the subject of this forum, this may not be the...

That looks more like a C# error than a SQL issue.

A brief Google search suggested this.

This link gives a few reasons for choosing shorter varchar lengths.

In terms of storage, CHAR(n) columns are always n characters long.

VARCHAR(n) columns are anything between 2 and (n +...

Datatypes look OK, except for one. Remember to size your VARCHARs to be the maximum expected length of the data they will hold.

You're probably better off using CHAR(3) for CPZ...

I suspect your GROUP BY is causing the issue. Try changing it to

GROUP BY TLD.location_id, TP.Location

Alternatively, I think modifying the default collation on your database before creating tables and adding data to them should also do the trick (and then you'll be able to write...

And that leads us to something like this:

SELECT *
FROM #temp
WHERE idaisl COLLATE SQL_EBCDIC037_CP1_CS_AS
BETWEEN basil COLLATE SQL_EBCDIC037_CP1_CS_AS AND eaisl COLLATE SQL_EBCDIC037_CP1_CS_AS;

• This reply was modified 3 years, 10 months ago by Phil Parkin.

My fault, I should have been more specific. The steps outlined above are assuming I know what the model will look (so after I've done the normalization on paper)....

If you can explain the requirement in English, I'm sure that someone here will help with the T-SQL.

It would also be useful to know the datatype of tab.x.

What collation is the DB2 database using?

And that works. But not incrementally.

So you want a process which compares what is in a database table with what is contained in a flat file and which then modifies the flat file to reflect...

I don't understand. When you restore from a backup it includes all the data from the backup. SQL Server does not do incremental backups.

The one big downside though is passing a multi-valued parameter to the stored procedure. IIRC - don't use SSRS now - it has to be passed as a single...

Try this:

INSERT #partsfeature
(
    PartId
   ,FeatureName
   ,FeatureValue
   ,PartFeatureNumber
)
SELECT s.PartId
      ,s.FeatureName
    ...