Try this...

IF OBJECT_ID('tempdb..#temp4', 'U') IS NOT NULL
DROP TABLE #temp4;
GO
CREATE TABLE #temp4(
Bdate DATE
,Country VARCHAR(7)
,Type VARCHAR(4)
,P1 INT
,P2 INT

I'm not sure if this is a concern with regard to your specific data, but if you you have a circumstance where the "latest 4" periods are all present (193,...

Is this what you're looking for?

IF OBJECT_ID('tempdb..#TempAgeAnalysisReport', 'U') IS NOT NULL
DROP TABLE #TempAgeAnalysisReport;
GO
CREATE TABLE #TempAgeAnalysisReport ([Account No] varchar(1),
     [Current] money...

I think you're making it too difficult... Just create an INSERT proc and a separate UPDATE proc. Then use a 3rd "control flow" proc to check & see on the...

Considering that you don't have the option to make this an actual DATE data type, I would suggest that you leave the data in it's current format. The YYYYMMDD is...

Q1... IIF is nothing more than a CASE expression with an abbreviated syntax. There is no impact, per se... You can use IIF or the equivalent CASE expression and produce...

If you need the dynamic version, try the following...

IF OBJECT_ID('tempdb..#temp', 'U') IS NOT NULL
  DROP TABLE #temp;

CREATE TABLE #temp (
  ID INT,

Try this...

IF OBJECT_ID('tempdb..#temp', 'U') IS NOT NULL
  DROP TABLE #temp;

CREATE TABLE #temp (
  ID INT,
  YDate INT,
  DE VARCHAR(200),
 ...

It would appear that you are correct about it being an NVARCHAR(128).

DECLARE @String VARCHAR(50) = 'this.is.a.test';

IF OBJECT_ID('tempdb..#temp', 'U') IS NOT NULL
DROP TABLE #temp;

Yes there are absolutely negative consequences to having too many indexes and/or the wrong indexes... As they say, there is no free lunch.
You can think of an index as...