no matter whether you like it or not, 1)application developers write managed code more; 2)application developers implemented the functions, including FORMAT, CONVERT, CAST, LTRIM, RTRIM, TRIM, LEFT, RIGHT; 3)FORMAT...

I did say reading the manual is advisable.

format 110 will give the mm-dd-yyyy you asked for the other columns.

and easier as you don't need the right function

format is very slow and should be avoided whenever possible.

it does help to read the manual

convert(date, dob, 105) -- 105 format is DD-MM-YYYY

full

select right(convert(char(10), convert(date, dob), 105), 7)

I'm not surprised after those 158 million rows deleted - most likely done all in one go.

depending on your system and on what space it takes on the log file to rebuild your indexes I would reduce the size of the log file - assuming I...

as per documentation (https://docs.microsoft.com/en-us/dotnet/api/system.data.datarow.itemarray?view=net-5.0) it converts each column of a row onto a  array of objects - and for each row on the recordset being retrieved it adds each column...

you do need to practice more powershell - and try out the combination of commands that you have available to look at the objects returned - main thing is to...

it is on each query as per example on the link I supplied

I think you're correct, you should do this for all tables.  No sense wasting resources scanning a 900-row table either.  Of course that 900 rows could be far larger...

you need to explicitly set the parameters db datatype - see https://stackoverflow.com/questions/19891999/how-do-i-force-sqlcommand-to-not-encode-parameters-as-unicode-nvarchar/19892033 for an example

one initial question - your query has lots of functions - as it is anonymizes we can't see what they are, but can you at least clarify what they are...

as a zip file it works as seen below - you may be able just to rename the .sqlplan to be .sqlplan.zip and upload it

• This reply was modified 5 years ago by frederico_fonseca.

estimate will most likely help - not as good as the real thing though.

as for the @variable - never saw that error on Plan Explorer - if you save the...

homework - final big work I would say.

when you are running the query you still not using Plan Explorer - that is all SQL Server on its own.

only once the query runs and SSMS produces the explain...