One thing that MIGHT be causing that problem...I believe the TEMPDB data file AND log file must be moved together.

-SQLBill

How did you try to change it. I have moved my TEMPDB without any problem at all.

Great article for moving system databases:

Moving System Databases - A Checklist by Christoffer Hedgate

http://www.sqlservercentral.com/columnists/chedgate/movingsystemdatabasesachecklist.asp

-SQLBill

I use a CASE within my WHERE to solve this type of problem.

WHERE CUSTNMBR =

CASE WHEN @CUSTNMBR IS NULL

THEN CUSTNMBR

...

It's the same as:

BEGIN

SET ls_action = 0

END

-SQLBill

You can not use a recent .ldf with an old .mdf. SQL Server knows they don't go togther and will give you errors.

You are going to be out of...

You can also use multiple columns as your primary key. If you think the barcodes might be reused some day, you could do something like:

Barcode Vendor

000001...

Probably the best way would be to create a stored procedure that SELECTs the data you want and then UPDATEs the bit. Then have your application run the stored procedure.

-SQLBill

Kevin,

That's not true. DBCC DBREINDEX (which rebuilds the indexes) requires the database to be in singleuser mode.

DBCC INDEXDEFRAG (which defrags the indexes) is an online operation. I use...

Okay, I'll buy that Steve...but my point is:

That isn't a "SQL Server 2000 constraint" (quote from original poster). That's a hardware constraint.

-SQLBill

quote: since usage has not been updated for a long time on this table.

So why don't you update the usage?

-SQLBill

What do you mean by the first transaction log?

You would restore your Friday Full backup, your Wednesday night Differential, and any Transaction Log backups made AFTER the Wednesday night Differential....

I believe the closest you can come in SQL Server (this is something that is normally left to be done on the front-end), is to use MONEY.

SELECT CONVERT(MONEY, ColA, 1)...

You are right about my results being wrong. Change the 1440 to 3600 in my scripts and it should return the correct answer. But it looks like you...

quote: I am not able to change the physical location of log file to a bigger disk because of SQL Server 2000 constraints. :endquote

What constraints? I moved my log...

This might give you something to work with:

DECLARE @mytime INT

DECLARE @myhour INT

DECLARE @mymin INT

DECLARE @mysec INT

SET @mytime = 3601

SET @myhour = (SELECT @mytime / 1440)

SET @mytime = (SELECT @mytime %...