Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
...and Oracle.
Also, it should perform as good as the NOT IN with the NULL, that was mentioned.
Put an index on the mobile number column in the second table if there's not already one there.
Assuming its a non-clustered index, you should be careful whether you add indexes or not. For something with alot of inserts/updates and few index uses it might not be worthwhile.
NOT EXISTS would be more performant than NOT IN in MySQL.
...and Oracle.
Also, it should perform as good as the NOT IN with the NULL, that was mentioned.
Put an index on the mobile number column in the second table if there's not already one there.
Leave a comment: