The SQL Server log should contain information about the trace start/stop events.

Start from there.

What do you mean "disable publishing and distribution"?

Without focusing on SSMS, what are you trying to accomplish?

Error 4145 is a syntax error.

If you're getting syntax errors, the code you're running is different from the code you expect.

Write it to a log file and see what's wrong...

Oh, I see what you mean.

Try this:

WITH T1 AS (

SELECT *, randowCol = NEWID()

FROM Target

),

T2 AS (

SELECT *, RN = ROW_NUMBER() OVER (ORDER BY randowCol)

FROM T1

),

T3 AS (

SELECT *, randowCol...

Duplicate post.

Replies here please: http://www.sqlservercentral.com/Forums/FindPost1562992.aspx

Well, it worked on the sample data you provided.

If you gave us more significant sample data, maybe someone could come up with something better.

BTW, SQL Server will try to use all the memory in the box, so having 80% memory usage is not a good thing. Having mem usage > 90% is normal...

IIS is running in the same box as SQL Server, then again I suggest that you lower your max server memory

WITH T1 AS (

SELECT *, randowCol = NEWID()

FROM Target

),

T2 AS (

SELECT *, RN = ROW_NUMBER() OVER (ORDER BY randowCol)

FROM T1

)

UPDATE T2

SET full_name_txt = (SELECT column1 FROM Use_value V WHERE RN...

Set max server memory to a smaller value.

My bad.

The subquery returns always the same value because it is not correlated with the outer query.

Well, looks like you solved your issue.

This could be one way to do it.

UPDATE T2

SET SomeColumn = RandomValues.SomeValue

FROM Table2 AS T2

CROSS APPLY (

SELECT TOP(1) SomeValue

FROM Table1

...

No, sorry, you have to do it in some other way.

MIME is basically BASE64 encoding, so maybe System.Convert.ToBase64String is your friend.

You could use an application lock.

Look up sp_getapplock in BOL

Basically, you could set the lock from the application and then put a check in a trigger.

Once you're done, release the...

Here's an article you can start from:

https://www.simple-talk.com/sql/database-administration/the-dba-as-detective-troubleshooting-locking-and-blocking/