You should get a performance improvement if you take the dynamic getdate() out of the queries ...

declare @now datetime

set @now = getdate()

INSERT INTO monitordata

SELECT * FROM data (NOLOCK) WHERE DATEDIFF(hh,time_stamp,@now)...

Agree with this. Alternatively, you could create a 'Payment Number' field (1, 2, ...) in both tables and then match on Voucher Number and Payment Number to perform the...

Sounds like you are performing integer division (the result of dividing one integer by another is an integer - so if the real result is < 1, the result you...

Hmmmm ... maybe you should accelerate your migration to SQL Server and all of your problems (well, this one anyway) will go away

I'd...

Aha. No, views do not exist in Access - the closest equivalent is a straightforward query.

You will notice in Access when you are building a query (using the 'create...

Quick solution ...

Haven't looked too much at your code - don't have two hours spare, but have you thought about creating 2 views (one...

When you say a 'local' database, do you mean SQL Server, or something else (eg Access)?

How are you performing the export?

I tried this using the DTS export table wizard and...

Check out the sp_rename stored procedure in BOL. Haven't used it myself, but it looks as though you can script your required changes fairly easily if you use it.

Regards

Phil

Launch Enterprise Manager and navigate to Management/SQL Server Agent/Jobs. Right-click in the Jobs window and select 'New Job'. Give the job a name and click on the Steps...

Please explain what Indian time is.

Your error message is not appearing - please add it to your post.

If SQL Server is powering a web app, you cannot buy a licence that refers to CALs and must instead purchase a 'processor' licence.

So you need the standard edition with...

Please post the query that is generating the error and details of how it is submitted - eg are you using a pass-through query in Access?

You may be receiving the...

Try this in Northwind (try varying the table_name in the WHERE clause) and you should be on the right track:

select a.constraint_name, b.column_name from information_schema.table_constraints a

inner join information_schema.constraint_column_usage b

on a.constraint_name =...

I actually think that the JOIN method will execute faster than the subquery I proposed. However, the subquery method is easier IMO to write and I had a hangover...