The documents you linked say that it MUST be CHAR or VARCHAR or be able to be implicitly converted to those datatypes.  According to this website:

https://www.sqlshack.com/implicit-conversion-in-sql-server/

The implicit conversion for CHAR...

Basically, the IMPLICIT transaction being turned on means you are going to need 1 additional "COMMIT/ROLLBACK" in your statement.  IMPLICIT TRANSACTIONS being turned on is like putting an extra "BEGIN...

The error is coming from the Snowflake ODBC connector.  I would check that it is configured the same on the server where SQL is hosted and on your visual studio...

Like Pietlinden, I am not sure what you are trying to do, but one way you could do what you are asking would be with a cursors and a while...

I agree with you ScottPletcher... I was just using examples (poorly) and bad terminology.  By "unhappy" I just meant that performance would likely not be great.  It is more that...

The "media" folder would be the folder that contains the installation media.  So wherever you are running "setup.exe" from is the folder you would use for that.

IF you don't have...

You should be able to use the default installation folder UNLESS it is asking for the installation media folder in which case you will need to point it to your...

I can answer question 1 for you - other transactions on that database that select data may have no issues.  Ones that change data will fail.

For question 2 - I...

• This reply was modified 5 years ago by Mr. Brian Gale.

I agree with Phil that it probably isn't a TFS issue.

Step 1 with debugging that for me would be to grab a different developer and have them try what I...

In the event you don't need unicode data in the body, you could convert it to a VARCHAR(MAX) as one thought.

Alternately, if you select the max length of the body...

Dimitri,

I want to apologize for sounding pessimistic about this.  I do see where the tool could be beneficial.  Where I work, it wouldn't be, but like you said, when you...

It is an interesting concept but it is still incredibly tricky to calculate.  Lets say I do partitioning on my table and throw all of the "old" data onto slower...

That is a nice and easy one:

 UPDATE [#partswithcompany]
 SET [companyId] = [PARTS].[companyId]
 FROM (SELECT [partNumber], MAX(companyID) OVER (PARTITION BY partnumber) AS companyID FROM [#parts]) AS PARTS
...

My opinion - I would install the R/Python stuff in SQL if you need it to store processed data in SQL OR you need it to process data that will...

The cause of having 58% sort operation is a 2 part question.  The sort is probably due to something on your clustered index so the data needs to be ordered...