Stephen, It would seem to be the new 10.0 client that is causing the problem. Reverting to the standard preinstalled SQL Driver sorts the problem out so at least I know now that the database integrity is intact which was my main concern.
There is obviously a setting in the new driver that is stopping the app seeing the blob data correctly so I'll investigate more but the problem is now not so urgent. The main problem with the old drivers is that they don't support the failover which is why I am doing all this data transfer as we have two servers now mirrored which at least I can now use, albeit only with manual failover until I sort out this problem.... but at least I have a working system and not 500 people baying for blood because all their document scans and pictures have disappeared!!! I'll keep you all posted. Dave -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Russell Sent: 13 February 2012 16:06 To: ProFox Email List Subject: Re: [NF] Urgent M$SQL help On Mon, Feb 13, 2012 at 9:37 AM, Dave Crozier <[email protected]> wrote: > Anyone any ideas about the following problem. > > SQLServer 2008 all patches on identical SQL Server machines. > > Database containing many tables with one table with Varchar(max) field for > holding blob data i.e M$ word documents etc... > > 1. Do full backup on one machine to transfer onto another identical machine. > 2. Restore backup to the new machine > 3. All blob data seems to be there but connecting with a program that can see > all the data on the original machine cannot see the Blob data > > Any Ideas... it's doing my head in > > Only difference is original database connected using ODBC "SQL Native > client" and the new database connects using "SQL Native Client V10.0". > > It MUST be something to do with a parameter in the connection string that the > new client needs but what is it.... > > > Working Connection : > Driver={SQL Server};UID=<<user>>;Pwd=<<Password>>;Persist Security > Info=True;Database=<<DB_Name>>;Server=<<Server_Name>>;Trusted_Connection=No > > Non Working connection: > Driver={SQL Server Native Client 10.0};UID=<<user>>;Pwd=<<Password>>;Persist > Security Info=True;Database=<<DB_Name>>;Server=<<Server_Name>>; > Failover_Partner=SQLB-FPL --------------- <http://www.connectionstrings.com/sql-server-2008#p3> Have you tried to remove the failover ? Driver={SQL Server Native Client 10.0};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword; -- Stephen Russell 901.246-0159 cell [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
