The standard trick is to import the header row as if it were data and then discard it in the data flow (use a Conditional Split to do this).

Also add...

Sorry, I've been doing this stuff for so many years that I have no idea about suitable training resources for you.

Sounds like triggers are your best bet. What sort of alert do you have in mind?

If a user modifies 5,000 rows, do you want 5,000 alerts generated?

If thousands of alerts...

In answer to your last question, the best you can do is

a) Describe what you are trying to achieve and what you want help with

b) Provide sample data in the...

• This reply was modified 2 years, 9 months ago by Phil Parkin.

Well, maybe it's time you learned a bit more. My script is straightforward and does the following things:

1. If a temporary table called #t1 exists, drop (delete) it
2. Create a...

If you open the link, there is a PDF option as well.

Is there anyway to import PDF file data...

Generate your own would appear to be the next resort.

I can generate my own uniqueID and I did that too but there...

Phil,

I can't create table (nor store procedures for example or views) because I don't have any other database access except for reading. Normally I import data and start working...

Yes. Provide your sample data in the form of CREATE TABLE / INSERT statements.

If you do that, others can copy the text straight...

What do you mean by 'fix' exactly? Do you want to generate a unique Id yourself?

• This reply was modified 2 years, 9 months ago by Phil Parkin.

You are dead right.

I'm so sorry guys, wrong CASE

(CASE WHEN CAST(DH.OPENING_HOUR_H AS INT) BETWEEN 10 AND 16 THEN 'Lunch' WHEN CAST(DH.OPENING_HOUR_H AS INT) BETWEEN 16 AND 19 THEN 'Snack' ELSE 'Dinner' END)...

I'd probably use a mapping table rather than a rambling CASE statement - makes the code easier to read, particularly if there are lots of distinct grades to be updated....

• This reply was modified 2 years, 9 months ago by Phil Parkin.

Not directly related to your issue, but there are a couple of good-practice items I suggest you consider:

1. Always qualify your tablenames with their schema
2. Try not to include DDL...