Using the query editor is the correct way to do it. The view/query designer in SSMS is fairly useless. There are a lot of SQL constructs it does not support...

If you want to ask a question which is related to an error message you get, you should always include that error message.

It would also have helped if you and...

Duplicate post. See https://www.sqlservercentral.com/forums/topic/rows-and-column-wise-total-in-sql-pivot-table for answer.

Here is a query for you. Note that I don't use the PIVOT operator, but instead uses SUM(CASE for the pivoting. This is somewhat more verbose, but also a lot...

I think the reason I and others assumed that you UDF made data access and a trigger therefore would be better is that your initial post talked about two tables....

That's not a valid XML document. Not even a valid fragment. Please post something that can stored in a variable of the xml data type.

Don't you have to specify the quotes as "?

It could help if you could include a sample XML document

A computed column with  a scalar UDF that performs data access? That's an absolute no-no in my book. Scalar UDFs are not inlined(*), and the the optimizer does not know...

It's not clear what you are asking for. The result set you post, suggests that you want to blank out tot_ship for rows but one. This can be done in...

Huh? There is no such limit. If you are only able to save images > 2MB ins size, you are doing something wrong.

How are you saving the images? Plain INSERT?...

The problem with EXECUTE AS OWNER is that the code runs with full powers of dbo, so if there is an SQL injection hole the possibilities for exploit is bigger....

The root cause is that you want the table and column names to be dynamic. In a relational database a table is supposed to model a unique entity and a...

It is always difficult to say without seeing the code and not knowing the system. But if you only pass a key around and read data in every procedure this...

The solution is simple. Don't shrink. There is no point in shrinking if you are going to fill up the space again. Also, shrinking the data files introduces a ton...

Two solutions. The first is somewhat obscure when you see it the first time, but works on all versions from SQL 2005 and up. The latter is more straightforward, but...