Use coalesce to replace the null value

set @log =   @Log + '  ,Date: ' + coalesce(@Date, 'NULL')

You can create an iTVF that will generate numbers on the fly

CREATE FUNCTION [dbo].[fn_GetNums](
    @low  AS BIGINT
  , @high AS BIGINT
)
RETURNS TABLE...

You could use a dynamic cross-tab query.  Take a look at the following 2 articles by Jeff Moden

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns

Cross...

You want to use SUM and not COUNT

Select distinct Model_id,
SUM(CASE WHEN Doors = 4 then 1 ELSE 0 END) [4DoorCount],
SUM(CASE WHEN Doors = 2 then 1 ELSE...

You either have to add a filter into your stored procedure, or store the results of your stored procedure in a table, and then re-query that table.

EXEC dbo.LogTable @Inserted,@Updated is outside of the catch block, so it will run after the rollback.

Also, @Inserted and @Updated are variables, which do not revert their value on rollback.  You...

Add the following to your WHERE clause

AND name LIKE 'DBA%'

If newtable exists ...

;with cte as
(
  select col1, col2, ...
  from ...
)

insert into newtable (col1, col2, ...)
select col1, col2, ...
from cte

If newtable does not exist

You've discovered the hard way why it's not a good idea to store dates in a char column.  That's not a criticism of you - I'm sure it's not...

It seems that if you simply add a '0' to the end of your string, it converts correctly

DECLARE @charDateTime char(22) = '2012-06-03 04:11:49:16';

SELECT CONVERT(datetime, @charDateTime+'0', 121)

If you change %3.00 to %3 then you will also remove the floating point issue.

I know that the OP stated that he was OK with NULL and All the same medals.

However, @luis soultion does not take NULL into account.

This should do the trick

            
October 11, 2019 at 5:46 pm
            
#3688107

            
            
                                                
        

A calendar table is definitely the better option.

But, just for fun, I have come up with 2 options that *SHOULD* work with SQL2000.  Unfortunately I do not have SQL2000 to...

the only days i would be exluding are weekend days (so no other holidays to be excluded).

so would a calendar still be the most appropriate way to do this?

I...

Historically, I have found that Stored Procs out-perform functions such as these.

• Try converting the function to a proc
• Try updating stats on the tables being referenced by the function.