And if you'd like to see some test results: Cast vs Convert

A bit old,but i think still valid.

AND t.StartExport BETWEEN CAST(left(convert(varchar,CURRENT_TIMESTAMP,120),10)+' 00:01:00.000' AS DATETIME) AND CAST(left(convert(varchar,CURRENT_TIMESTAMP,120),10)+' 16:00:00.000' AS DATETIME)

Nice,failed due to the right justified result of STR.

2 points?:cool:

Missed the missing ALL. Where is my coffee again?? 😀

In my opinion it's unimportant, if the other indexes are disabled or not. You can't reach the table data with a disabled clustered index.:-D

Link is already in my first post, but please: https://msdn.microsoft.com/en-us/library/ms187810.aspx

If we assume, that we have the latest SQL Server Version (2014), then an over by is required according to BOL (I can't try it yet)

OVER ( [ partition_by_clause ]...

Hmm. According to BOL, if OVER used with a SUM, then an order by clause is required...

Nice question!

The linked reference states: Because the xml data type methods cannot be used directly in creating computed columns...

Without running the code i thought, the variable declaration will throw an error.:-D

(Just to be sure: aren't we in the 21st century? :cool:)

:doze:

I hate myself not to read the relation correctly! 😀

I thought it'd fail at:

CREATE PROCEDURE [TEST].[PopulateAddress] (@Address AS TVP.Address READONLY)

BOL has no reference to this 'AS':

[ { @parameter [ type_schema_name. ] data_type }

...

The data seems to be in EDI X12 format. Maybe here you will find more details about it.