You don't have to use replace - the string will be converted (implicitly) to an integer for comparison so any leading/trailing blanks will not affect that conversion.

You...

You don't have to use replace - the string will be converted (implicitly) to an integer for comparison so any leading/trailing blanks will not affect that conversion.

You can also...

In the original version, try putting brackets around the column name "Kolicina".  It looks like you might have a non-standard character in the name.

I'd stick with temp tables.  And it can't hurt -- and could help -- to use a PK in the temp table (or table variable).

DROP TABLE IF...

See if these calcs give you results more like what you want.

Edit: Note that the calcs are completely independent of any/all date and language and DATEFIRST setting and will work...

• This reply was modified 5 years, 1 months ago by ScottPletcher.

If you build nonclustered indexes as necessary,...

If you tell us what you consider to be a "week" -- as we asked for several times -- we could give you code specific to your needs.

I wouldn't rely...

Well, obviously, I don't consider it "stupid".  Remember, the DELETEs are almost twice a minute.  If the table has to be scanned in order to do the deletes, that would...

You're welcome.  Yeah, SQL requires the alias name (the "AS" is not required, I just like to use it but the "any_name" part is required).

You need parentheses to "tell" SQL you're using a subquery in the SELECT:

SELECT * INTO temp_Weekly_Event_Report FROM
(
SELECT

DISTINCT column1 FROM [SQLDatabase].[dbo].[Table] WHERE Event_Source = 1
) AS any_name

I strongly object to starting with table structures.  Data normalization is a logical process, tables don't exist yet.  It's all about the data itself.  One should be referencing entities and...

They have a query that runs 2400+ times a day using that column to DELETE from the table -- I stick with my recommendation, cluster the table first by that...

Always use IFI unless you have disk data that you really can't have anyone else see via some type of hack.

Data pages do not need to be zeroed out before...

I think it can be simplified a bit, while also allowing for another value to be found in the future (maybe 'null'?):

SELECT
    LongString,
 ...

Most likely that's still best.

Btw, do you know for certain that a given product only occurs once on each order?