Or use dynamic SQL. That would work as well.

I suppose snapshot replication would be overkill... but still an option!

Good luck!

Glad you sorted it out.

Another way could have been declaring Conn without type declaration (it becomes a variant that way) and then assign the object:

Dim Conn

Set Conn = createObject("ADODB.Connection")

Quite true, but you could batch UPDATEs to set the column to NULL. Once every row is set...

Lowell (1/12/2012)

---

for something similar, we've created the parallel table without the image column, migrated the data, then renamed the old vs new table, and after we were sure everything was...

Another option: OSFMount

An alternative method...

WITH SampleData (Entry) AS (

SELECT 8.55

UNION ALL

SELECT 90.07

)

SELECT Solution = REPLICATE('0',(3-len(floor(Entry))))+ cast(Entry as nchar(20)),

Alternative = REPLACE(STR(Entry,6,2),SPACE(1),'0')

FROM SampleData

I have no idea what that CLSID is, but this article (on a totally different topic) describes how to grant launch permissions on a CLSID on Win2008:

http://www.sqlservercentral.com/articles/Linked+Servers/73794/

Hope this helps

Gianluca

What do you mean with "fail"?

Care to share the error message?

Don't overlook Brandie's suggestions. Fix the server first of all.

IMHO, no. Taking FULL backups is much easier.

I see. What about moving the binary data in a separate filegroup and perform a partial backup?

Compression won't probably help in this case, because images are usually already compressed.

Yes, it can be done moving the table to a different database and creating a view with the same name in the original database.

Be careful: some things, such as foreign...

+1

This is the case most likely.

Another good reason not to use NOLOCK.

Then, I think there's not much you can do.