You need to use an update. Yes, update replaces the value, so make the new value contain the old.

UPDATE SomeTable

SET SomeColumn = SomeColumn + 'Another string value'

btw, this is a...

Shawn Melton (1/14/2016)

---

Will also note though that opening the Live Data Viewer attaches a different target to your session called...

Then that's your problem, not the maintenance. With no indexes at all, no clustered index, the table is a heap. Firstly index rebuilds won't touch heaps, second deletes don't deallocate...

As I said,

Distribution *is* a system database.

Events don't show up instantly in the live data view. They're not dispatched instantly either. Run your queries, wait a bit (oh and make sure that you started the...

What indexes does that table have?

That's pretty immaterial. To do what you want requires a case...

And...

This is the reason we don’t include Clustered index columns in Non Clustered indexes because even though you mention clustered index columns as a part of your non-clustered index key...

Go into the maintenance plan and enable logging. You need to see the actual error to fix whatever's wrong.

Nope.

If you're looking for improved performance, don't waste your time fiddling with partitioning. Partitioning is for...

Don't restore system databases from one instance to another, doing so is asking for subtle problems.

Script the logins, linked servers, config settings, roles, jobs, replication out and use those scripts.

No. Master can't be restored from any other version, and to be honest you shouldn't be moving most system DBs from one server to another. Script their contents, recreate. In...

Within the trigger, something like

INSERT INTO AnotherTable

SELECT <whatever columns needed> FROM inserted;

Join to sys.dm_exec_requests on sessionID and then CROSS APPLY to sys.dm_exec_sql_text using the sql_handle column in exec_requests. I think the column's there in SQL 2008.

Alternately if you know there's a...