If you remind yourself normalization rules you'll see the design is wrong.

No tools can help here.

Bottom line:

Fix the database design.

If you connect to SQL Server as "sa" then the only name you can catch is "sa". This is the user running queries.

If you want to know the user name...

I support Robert.

What you really need is UDF to split your strings into proper set of Version, Subvirsion, etc.

Then you may order by parts.

If you could explain the logic of your sorting in plain English...

SELECT ReportCol

FROM (

select PL, NULL as SEQUENCE, PLDescription as ReportCol

FROM

(

--Select all Items from MAS200 excludeing then ones that are Web Exclude

SELECT dbo.IM1_InventoryMasterfile.ItemNumber as ItemNumber,...

Remove "{" and "}"

Next time start from BOL.

Use sp_MSforeachdb

SELECT ReportCol

FROM (

select PLNumber, NULL as SEQUENCE, PLDescription as ReportCol

FROM {YOUR TABLES}

GROUP BY PLNumber, PLDescription

UNION

select PLNumber, ItemNumber, ItemNumber

FROM {YOUR TABLES}

) DT

ORDER BY PLNumber, SEQUENCE

Simple question:

How many columns you expect in returning resultset?

Take Robert's solution as a sample and build the script dynamically.

Right-click on database in EM.

Select All Tasks -> Generate SQL Script.

Read attentively and choose items carefully.

For job to fail a step inside this job must fail.

Create a new step for sending SMS.

Set this step to be executed only on another step failure.

I meant not what you meant but what sql 2005 fan meant.

Hope you followed who meant what.