This will do what you want, but without the identity (all the values will be unique but many numbers will be skipped).

Select Distinct C.name, (Select count(*) from dbo.SysColumns C2 where...

Have you considered my advice on keeping the work_ord_num in a separate column so that a index seek can be used? You'll see a huge speed improvement even on...

I think you could have an instead of update on views that could be coded to reinsert the data in the base tables.

But you could also have a table or...

You don't need temp tables to do something like this. Views will do the job just fine for this task.

I'm not sure I'm following here :

10 tables = 10 views, any problems with that?

How are the users gonna request the data?

As far as I understand : if sql can't write to the log, it will not execute the statement. The word critical should also be self-describing.

Can you imagine the implications of that possibility?

You could also set the recovery mode to simple so the log takes less space during this operation.

Read this for a solution.

The Curse and Blessings of Dynamic SQL

if update ([name]) or update(col2) or update (coln)

...

The rest seems fine. One thing that can save a lot of cpu cycles is to check that any actual data has...

CREATE PROCEDURE dbo.spGet_bag_nums

@work_ord_num char(6),

@work_ord_line_num char(3),

@bag_nums varchar(8000) OUTPUT

AS

SET @bag_nums = ''

SELECT @bag_nums = @bag_nums + CAST(bag_num AS VARCHAR(10)) + ',' /*so you can resplit them on the client*/

FROM dbo.tblBag_data

WHERE LEFT(work_ord_num, 6)...

Try this :

WHERE B.dbo.TempOrders.OrderID IS NULL

Well you can create a view for each table and grant access on the views. That way they can update/insert/delete data if they need to but they don't have direct...

You're pretty much asking for an omelette that's eggs free. You cannot have a unique value that is not unique to all rows.

What r u trying to achieve by...

I think that this would be a simpler version :

CREATE FUNCTION dbo.RemoveTime (@DateTime as datetime)

RETURNS DATETIME

AS

BEGIN

RETURN DATEADD(d, 0, datediff(d, 0, @DateTime))

END

GO

Select dbo.RemoveTime (GetDate())

drop function RemoveTime