I think the only thing that would happen is you don't get the EE features like Data Driven Subscriptions. But I think it is legal..

CEWII

Putting your assembly in the GAC does not make them available to SQLCLR, they have to be added to the SQL server database before they can be referenced. Using...

I am 99.999% sure that you can't get around this, 64bit sql demands 64bit extended stored procedures..

CEWII

In many cases in the Dataflow you can catch a bad row by configuring an error row output, after you drag the red output to its path you need to...

You could try wrapping a try/catch around them. But I REALLY have to recommend the SSIS solution instead.. Also keep in mind a connection in SSIS or as...

I agree, if the config file contains the connection information and the package configuration is configured to use the file it WILL use them, that is what forces it too..

CEWII

Let me see if I got this. Site A has SQL and also SSRS, Site B has SQL and also SSRS.

Are you talking about losing site A? IF so...

I am assuming you are referencing the client machines. In that case you can use whatever is appropriate for the client and the application.. A 64-bit server does...

The clustering handles that. When it fails over it stops resources on one node and starts them on the other.

CEWII

I think I have that one at home, I liked it. I thought it was pretty good..

CEWII

THe short answer is Package configurations. Now the more tricky question is where to store them, there are several choices:

1. XML file

2. Environment variable

3. Registry

4. A Table in SQL

There...

I believe it reflects whether the process returned an ERRORLEVEL other than zero. There is a field called SuccessValue in the process tab of the Execute Process Task editor,...

I would love to know a better way to do this..

But I have done this by using xp_instance_regread and reading the AuditLevel and the LoginMode reg entry. On my...

First of all User-Defined functions are read-only constructs, they CANNOT modify data. With that said you CAN use stored procedures to encapsulate insert/update logic. It could be you...

I believe the issue you were experiencing is called Parameter Sniffing. There is a really good article here:

http://omnibuzz-sql.blogspot.com/2006/11/parameter-sniffing-stored-procedures.html

That explains it far better than I can..

CEWII