Please explain...

Thank you very much for the responses - I'll look into the partition switching idea.

Phil

Silence! Any ideas anyone?

Gazareth (2/2/2012)

---

Ah, thanks Phil, I didn't know that.

Although if you're doing all that, I wonder why SSIS would be used at all in this case.

Surely at that point SSIS has...

Koen Verbeeck (2/2/2012)

---

Phil Parkin (2/2/2012)

---

That's not quite true, though it certainly isn't as easy as it might be. If you...

That's not quite true, though it certainly isn't as easy as it might be. If you are prepared to venture...

So you are just ignoring almost all of the advice everyone has given you and still asking for help?

If you are not prepared to listen, or at least to...

Not sure, but have you tried using an expression, rather than parameters, to do this? Then you can quite clearly see where your variables are going.

You could also try something...

rishiextc (2/1/2012)

---

You can do it as follows,

1. SET IDENTITY_INSERT Table_name ON

2. INSERT into Table_Name (Column_1, Column_2......) Values (Value_1, Value_2.....)

(make sure while inserting you specify name of required...

That's how IDENTITY columns work. Read more here.

If you really want to reset the seed value, read up on DBCC Checkident.

If you rewrite your proc slightly to use dynamic SQL in the non-validating bits, you can get round the validation issues.

Once you've built your dynamic SQL string, try doing a straight

select @sql

before executing it. That should allow you to see where things are going wrong.

No problem.

I was responding to this statement:

I generally use SQL2K8 and i'm used to the format on it. Unfortunately the company i'm working for are on 2K5 and they're not...

What is there about your proc which works on 2008 and not 2005?

I explained the behaviour of STR() (or so I thought).

For your purposes, it is not suitable. If instead you cast your variables as, say, varchar(30) and then print them, you...