JK (Same first initial and last name as my brother - trivia point)

This must be an abbreviation of your works since it seems the only reason to use the Register...

Previous versions used to say (I think) 17KB per user. I think the formula is simply 12KB + (3 * Network Packet Size). I know it looks like...

You may want to review index structure and exeution plans. We have run multiple databases on one machine for years without significant performance issues.

Making a second connection is fine...

If all your programming will be "guaranteed" to run in your time zone, you could just use a DATEADD( HOUR, 6, <DateInDB> ) to display the correct time.

If you want...

It appears that there are some conditions missing. For example, the update billable_temp statement does not restrict the entries to a specific area code.

Would it work for you to...

With that many users, take a look at the per server license - yep! It's a wad of cash too, but not as bad a per seat.

Take a look in...

Depends an awful lot on how the updates will take place. If there needs to be specific processing for each row, the CURSOR will work. If you can...

You need to assign the value

SELECT @val1 = val1 FROM tblTemp1 WHERE rowID = 1

Guarddata-

Look at the result of the ENCRYPT function. All it does is write the output in pseudo-double byte hex format of the original string. You could look into...

While this shouldn't loop forever, I imagine you actually want something different. First, you are not using the value read by the cursor. The statement of INSERT INTO......

No problem at all. I have great respect for your abilities and have learned much from your posts. I also wish people would just post to a single...

SQLBill, I am sure you didn't mean for your message to sound the way I read it. There are a number of ways to address most issues so there...

Just one result set? Sure.

Create temporary table

cursor

insert into temptable

exec sp_executesql @selSQL

deallocate cursor

select * from temp table

(Hope that's not too sketchy)

Guarddata-

Oops - went horizontal when you wanted vertical

DECLARE @colName VARCHAR(30)

DECLARE enabledCol CURSOR FOR

SELECT columnname from TABLE WHERE ENabled

OPEN enabledCol

FETCH NEXT FROM enabledCol INTO @colName

WHILE @@FETCH_STATUS...

Hmmmm - I may be missing something. Isn't it true that if you FETCH NEXT without using the INTO option that the resulting dataset is just returned to the...