So, are you ready now to agree with my inital statement "Don't bother to drop temp table"?

Or you gonna insist on "best practices" to drop it?

Can you look at space used by each table in the database?

Seems you're barking on the wrong tree.

Example from BOL:

SELECT *

FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',

'Data Source="c:\Finance\account.xls";User ID=Admin;Password=;Extended properties=Excel 5.0')...xactions

"xactions" here is the sheet name, [Sheet1$] in your case.

You need to shrink whole database at the end of process.

And this part must be done definitely off hours. It will consume as much server resourses as it could reach...

No, it means 2 days + 0.7*24 hours. "2.7" days.

SELECT COUNT(OrderID) as [Total number of orders],

COUNT(case when ReceiptHours <= 24 then OrderID else NULL end) as [24...

Does your C:\Project.exe actually work?

What are the conditions when C:\Project.exe does the job?

What happens when you run

execute master.dbo.xp_cmdshell 'dir c:\'

Is file "project.exe" in the list returned?

Is OPENROWSET what are you looking for?

Or you are asking about something more specific?

Datetime value will always have part time. That's why it's named DATE-TIME.

The best you can do is to make time part = 00:00:00.000

Is it what you are after?

Yes, really amusing.

Guys decided to show how smart they are, but did not realise whom they are dealing with.

jezemine, sorry, but you are...

The matter of fact it's not A best practice.

You cannot provide a single fact to prove that this practice is better than mine. You even admit it affects server performance...

That's all you can provide as a proof for your "best practices"?

"I disagree just because I disagree"?

We can agree that you statement about "best practices" is wrong.

I proved that all you assumptions and statements in favour of dropping #tables were wrong.

You cannot find any reason why...

To make sure you are really knowledgeable about the subject you better run some tests.

Because the text above says you are not.

CREATE PROC dbo.ScopeTest

AS

SELECT TOP 1000000 IDENTITY(int,1,1) as ID,...

I assumed from the question that distances will be loaded from somewhere, not calculated.

What they need is the prepared "pattern" to fill up with data.