Just to clarify your terminology, you can't create a SQL login and map it to a Windows login.  You can create logins on the SQL Server for Windows users and...

Can you make the Remaining parameter a field in the returned recordset?

I've been around long enough to know that there is a wide spectrum from early adopters to "If it ain't broke, don't fix it" attitudes out there, and many reasons...

There is a Description property available for each field and table in either Enterprise Manager or Management Studio.  It's an simply an extended property named "Description".  sp_addextendedproperty will let you add...

Another option might be to use Generate SQL Script in Enterprise Manager.  Select all the desired objects and look at the formatting options to make sure you get everything (indexes,...

SQL Server/Access would be the cheapest/easiest route.  Migrate the data to SQL Server 2005 Express (which is free), and either keep the existing Access front end or migrate to a...

You could do it all in a SQL task:

WHILE NOT (...) WAITFOR DELAY '00:05:00'

I didn't want my reply to Todd to sound testy.  I believe he was expressing an honest opinion when he said he had only seen minimal speed differences.  I have...

I don't want this to sound like a flame, but if you haven't seen a speed difference between a DTS data pump task and a bulk insert then either you...

Create a dummy SQL user in each role, and then the admin users can use SETUSER to impersonate a user in any role.

I guess it would depend on how much the specific functions optimize the operation compared to a general-purpose function.  Run some tests and see if there is a noticable time...

The standard ultra-ultra-conservative reaction is you don't use the first release of anything in production.  Like my father would never buy a car the first year...

I ran into this often enough to create a general-purpose function.  The @type parameter should have a bit set for every class of character you want returned; 1=alphabetic, 2=numeric, 3=alphanumeric, 7=alphanumeric...

use

msdb

-- Find the Job ID and the step numbers involved

declare @new_step int

declare @jobid uniqueidentifier

select @jobid...

I think it's spelled out better in the SQL 2005 documentation:

"SET ANSI_NULLS ON only affects a comparison if one of the operands of the comparison is either a variable...