Create a script that will step through the existing user accounts (sys.sysusers) and delete those that you don't want and that don't match up to sys.syslogins. Then have a...

Check out sys.sysusers. The "sid" column matches up the PK in sys.syslogins.

There's a good article on string splitting (and related Numbers table functions), here: http://www.simple-talk.com/sql/t-sql-programming/the-helper-table-workbench/

Something like this:

select *

from MyTable

where datepart(minute, [Date and Time]) = 0;

That should give you the rows that end on-the-hour.

select *,

(select case when exists (select 1 from MyTable as...

Is it possible there are two versions of the login, tied to different server-level user IDs?

The trigger simply selects from "inserted". That'll handle multi-row inserts.

I would suspect constraint/nullability violations, or explicit/implicit rollbacks.

Are you familiar with the various date and time functions in T-SQL?

You could query the table Where datepart(minute) = 0 and get all the rows where it's on-the-hour, and then...

Update will take the locks it needs.

You might look into isolation levels. Snapshot (couple of flavors here) isolation can really improve concurrency in some cases.

I use a CLR function for that. Would that give you what you need?

What "properties" are you looking for? Stored procedures don't have a "properties" tab that I know of, whether server or user-built.

The usual way to do this kind of thing is:

select Col1, Col2, DateTimeCol,

(select min(DateTimeCol)

from MyTable as MyTable2

where MyTable2.Col1 = MyTable1.Col1

and MyTable2.Col2 =...

You're welcome.

You're welcome.

All Profiler does is run a trace. Create a server-side trace, and you can have it run constantly or you can use an SQL Agent job to schedule it...

If I'm following you correctly, you have a task that fails (on purpose), and it has an on-failure path from it, which isn't being called when it fails. Is...