OK, two things. First, trust but verify. In other words, don't believe what people like me tell you without checking it out for yourself. Read that link...

Bizarre. Please will you post your SQL statement?

Thanks

John

If the affinity mask is deprecated, then I wouldn't go anywhere near it. You don't want to have to devise your solution all over again when it's eventually removed.

John

Read the link I posted earlier carefully. I think it says that for ADO, your parameters should appear as param1, param2, ... in both the parameter list and the...

Check that your ForEach Loop is configured to write the value(s) from each row into variable(s), and that the variable(s) is mapped to the parameter(s) that you are passing to...

See here. ADO.Net doesn't use the ? as a parameter marker. In any case, why are you doing this with a ForEach Loop? Sounds like the kind...

As Dev suggests, ditch the ORDER BY. The only thing that will guarantee sorted results is if you use an ORDER BY when you call the view, so leave...

I haven't done all that much flat-file exporting with SSIS. But aren't there all sorts of options that you can configure in terms of the output file? If...

How are you doing the export?

John

You should leave the displaying of information to your presentation layer. If you must use T-SQL, this'll get you most of the way:

SELECT 123456 / 100.0

John

Possibly, but I've only ever seen the "Agents XPs disabled" notice next to the SQL Server Agent icon in Management Studio - and you can only see that if SQL...

Not just errorlog, but also sqlagent.out. If you don't have a sqlagent.out, then that's probably the problem - the service is configured to write to a folder that doesn't...

I don't understand why you're using a Script task. I would use an Execute SQL task, with an expression built using the values from your columns. If this...

I searched the internet for "create solution in bids". If you do the same, you'll find...

Lowell (12/12/2011)

---

i'd recommend forgetting about putting the count in the table.

instead, create a view that is uesed to calculate the count based on a join; then the count is correct...