Nah, probably my only readers are my mother and girlfriend

What you're talking about is referred to as "row-level security". This is a good introductory article:

http://vyaskn.tripod.com/row_level_security_in_sql_server_databases.htm

If you have more specific questions once you get going, post back...

How big is your partnumber data?

Would you mind telling me:

A) The data type of the column

B) the output from:

SELECT AVG(LEN(PartNumber)) AS AvgLen,

MAX(Len(PartNumber)) AS MaxLen,

MIN(Len(PartNumber)) AS MinLen,

COUNT(*) AS Count

FROM...

Thanks, Tal! I'm sure that will be very useful. Are you hosting that? Do you mind if I link to it from my blog?

I've read in various places that PATINDEX was faster than LIKE, but have never been able to reproduce it on my end. Can you post some code that proves...

If you're using SQL Server 2000, I recommend that you use SCOPE_IDENTITY() instead of @@IDENTITY. The latter will return the last identity generated for your session, whereas the former...

What type of dependencies? If there are foreign keys referencing the column, or if it is indexed, you will have to drop the keys/index in order to drop the...

Garry,

No, you cannot do that; the INSERTED and DELETED tables will have the same columns and datatypes as whatever table the trigger fired for.

No worries, you've got me beat by 3300 posts already ... Too bad there's not a prize

You can use a CASE expression for this:

UPDATE Table

SET qty_total = CASE WHEN (start_qty - end_qty) < 0 THEN 0 ELSE (start_qty - end_qty)...

I think you want something like:

select *

from IV10200

where daterecd =

(SELECT max(daterecd)

from IV10200 i1

where i1.itemnmbr = IV10200.itemnmbr)

Russell, you can use parameterized queries for that purpose. Performance gains of stored procedures over parameterized queries are really not an issue at this point (IMO) ... unfortunately, people...

Also, I just found this KB article that might apply:

http://support.microsoft.com/?id=312995

Are you sure you updated the correct instance? If you're running multiple instances, you do have to run the update on each instance separately. If you're not running...

I recently discussed my feelings about this in my blog... You can read them here:

http://sqljunkies.com/WebLog/amachanic/archive/2004/10/26/4823.aspx

... the jist of my argument is that stored procedures may not necessarily be better...