To use CLR stored procedures, your database needs to be in Compatability Mode 9.0 (SQL Server 2005).

I am assuming that you have created some procedures in the master database that you have named sp_xxxx. When you run those in a user database are you calling with...

When we upgraded our PeopleSoft Financial System database from SQL 2000 to SQL 2005, we had similiar issues.  We initially used DTA to identify new indexes, and ended up adding 37...

Fully aware of using SQL to start jobs, or using xp_cmdshell to execute command line programs.  Starting a job is asyncronous, and would require additional coding in both the job...

This is the link in BOL I started my research with:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/dtsref9/html/2f9fc1a8-a001-4c54-8c64-63b443725422.htm

Could you also provide the full code for the stored procedure?  One thing most will jump on is the possibility of parameter sniffing (search this site for more info on...

At my last employer we logged ftp transfers to a SQL Server database table on one server (using virtual directories, the files actually we loaded to a second server) to...

Why would I need to allow and use unsafe assemblies in the database?  So far in my research I haven't seen that, but of course, I may not have gone...

Glad to help, and from what you said above, I assume it worked okay.

Okay, I was looking at one of my packages, and I think I know what you need to do.

Edit the Execute Process task.  Select Expressions.  Click on the ellipses button...

Please post, at least, the tables ddl (what do the tables look like?)

It really is only a work around.  If your table gets big enough, it will stop working.  A view, returning all rows is treated as a table, the order of...

I've noticed if you cut and paste directly from QA or SSMS (where everthing is single spaced) ends up double spaced here.  I usualyy use UltraEdit as an intermediare so...

select top 100 percent ... ORDER BY ..., SQL Server 2005 ignores the order by clause.  This is actually how it should be handled.  There are several discuss threads on...

The problem you are having is a collation conflict.  Somewhere in your query, you are comparing two character fields that have different collations.  Without knowing which tables are using which...