Technically, a bit value of 1 is true as if you print the variable, you'll see 66 has implicitly converted to 1.

Good idea for a QOTD, I wouldn't have guessed...

Have you tried inserting through OPENQUERY? This runs the statement on the linked server end rather than the SQL Server:

http://technet.microsoft.com/en-us/library/ms188427%28SQL.90%29.aspx

According to BOL, * is defined as:

prefix_term

Specifies a match of words or phrases beginning with the specified text. Enclose a prefix term in double quotation...

Ah, yes, I understand now. It was mainly the +2.000000 in the calculation that was confusing me, but I get it now, it's just that you're picking the dates inside...

This makes my head hurt, but trounces my solution 😀 (I've converted yours to update the source table as per the query instead of outputing to select). Results below:

Table 'mytable'....

Nice one. Hadn't thought of doing that!

Well, with my data, the original method and with Benyos's clause gave consistently the same time (give or take .5 secs), but the extra...

Well the Inner Joins restrict the data set to only NULL yields anyway, but I'll give it a spin and see if the execution plan/performance changes after adding that.

I'll also...

What format is the date that's stored as an nvarchar? Only certain date styles are implicitly convertable from nvarchar to datetime.

How are you importing? (e.g. the Import/Export Wizard/SSIS?)

I'd suggest that...

sys.sql_modules preserves line breaks, it's the SSMS grid view that doesn't. If you return the results to text, you'll see that the line breaks are there.

My only guess would be that in establishing the connection through SSMS it is triggering a firewall/AV rule at either end that is then blocking further connections for 10 minutes.

I've...

That's news to me as well. Good spot.

Or...

SELECT department, COUNT(*) as "Number of employees"

FROM employees

WHERE salary > 25000

GROUP BY ALL department;

The thing is I suspect it would be slower with a large dataset. If you want to preserve both rows in the event of a tie, use rank() rather than...

Individual locking hints in queries shouldn't really be necassary.

Have a read up about Isolation Levels and see which is appropriate to your application:

http://msdn.microsoft.com/en-us/library/ms173763%28SQL.90%29.aspx

Well, there should be no difference between the results from what I can see. What problem are you having?

The view is redundant however...

The view may perform marginally worse as the...