Hi Carlo,

sysdepends is notoriously unreliable due to deferred name resolution - which means that I can create a stored procedure before the objects it references exist.

In the stored procedures I...

I've been waiting a long time for an article like this.

Finally kerberos is explained in words even I can understand.

Well done!

I've since found another couple of issues. One is that it in the same way as I need and #endchars table to stop table1 matching on table12, I would...

Thanks Ian, that's a useful thread indeed!

Hi Ian,

I think you've misunderstood my question.

*= syntax will work under compatibility mode 8 (2K). It wont under level 9 (2K5).

I was talking about 2K5 features that still work...

ok...fair enough. A bit of dumb on both sides!

yeah, me too. I don't get it!

Plus the question is wierd, as they're a 2005 feature. And answer 2 makes no sense, given the question.

But it is early....so...

I'd always go for separate databases, for a number of reasons, but starting with a drawback, you can't use DRI across databases, so you have to enforce Referential Integrity some...

I was vaguely aware of this behaviour from UNION, but a perverse idea occurred to me reading this article.

Why not use UNION instead of DISTINCT or GROUP BY?

SELECT a, b...

In short you do

CREATE PROC myproc AS

followed by your SQL

and then you run this on your database which creates the stored procedure. Then on the SSIS side in the...

le 'probleme' (ce n'est pas le mot que j'employerai) est que si tu mets le sql dans SSIS, il essaiera d'envoyer cet SQL par la voie ODBC ou autre selon...

Oui, il y a une solution....celle que je t'ai donné.

Yes, there is a solution....the one that I have given you.

You can use it or not - c'est ton choix.

ce que tu dois comprendre c'est qu'il faut PAS mettre le sql dans SSIS!

Il faut mettre uniquement le 'exec xxxxxxx' dans SSIS.

desole...mais je n'ai rien compris de ta reponse! Peux tu etre plus clair...avec des exemples.

Faut remplacer les 😉 avec une )