Comments
Sort by recent activity
On further examination it would appear that function handling in general is inconsistent. DATEADD breaks after it's commas regardless of the setting of "commas first". CONVERT does not break at commas. / comments
On further examination it would appear that function handling in general is inconsistent. DATEADD breaks after it's commas regardless of the setting of "commas first". CONVERT does not break at com...
relinking didn't work, I've had to create a new folder in the repository for now.
Any thoughts on the "hunting down" part? any logging I can look at to see where it's falling over?
Just sent file. My bad, didn't notice that option before! / comments
relinking didn't work, I've had to create a new folder in the repository for now.
Any thoughts on the "hunting down" part? any logging I can look at to see where it's falling over?
Just sent file. ...
Just found I can prevent this behaviour by assigning an alias after the function / comments
Just found I can prevent this behaviour by assigning an alias after the function
Workaround confirmed, thanks Aaron. / comments
Workaround confirmed, thanks Aaron.
I've seen the same thing. I had a couple of tables with nvarchar primary keys. I have worked around it by putting in an int primary and having the original key as a unique but that's not always going to be possible. It seemed a bit like when you use CHECKSUM for a dimension, it ignores certain characters. I'd be interested to know why a binary comparison isn't the default. / comments
I've seen the same thing. I had a couple of tables with nvarchar primary keys. I have worked around it by putting in an int primary and having the original key as a unique but that's not always goi...
I am also seeing this. In SPs with 5 or more temporary tables.
I have gone back to 5.1.4 and find that the problem is far less pronounced. It still has high CPU activity but for much shorter periods making it workable. / comments
I am also seeing this. In SPs with 5 or more temporary tables.
I have gone back to 5.1.4 and find that the problem is far less pronounced. It still has high CPU activity but for much shorter period...