Re: Spin/ spout BCDL to sql server Swap (how do i stop sharepoint using BCDL?)

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Stephen Woodard[MS] (stewood_at_microsoft.com)
Date: 09/10/04 

Date: Fri, 10 Sep 2004 13:01:17 -0500

I am not sure if I understand your question.

Spin/Spout just copies the documents and meta info into SQL. It does no
redirection. If you still have the BCDL installed and users are editing
that version of the document they will not be going into SQL.

Your users should access the documents in the location you 'Spouted' them
too. If it is confusing to your users I would remove the BCDL if you are no
longer using it. 

-- 
-Stephen
 This posting is provided "AS IS" with no warranties, and confers no rights.
"alrix" <alexandra.rix@sonybpe.com> wrote in message 
news:4a0323e.0409090230.69948248@posting.google.com...
> Hi,
> I've upgarded from Sharepoint portal server 2001 to 2003 and have
> managed to install the optional BCDL components (backwards compatible
> document library).  We also use as a configuration database etc, a
> remote sql server database.  I have imported topics into the portal (I
> have created virtual servers and thus one portal per workspace in
> 2001). I can view the documents etc without a problem.  I run
> Spout.exe against the 2003 BCDL and spin.exe.  All works ok.  THEN, we
> check the documents exist in SQL server, and they are there, but, when
> we update a document through the portal, there is no change to the SQL
> server data.  i.e. the portal seems to still be pointing to the BCDL.
> Any ideas how i can stop this/ force it to point to sql server?  I
> checked the components on the server admin page in sharepoint all
> reference the remote sql server correctly.
> thanks

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • It can be Done
    ... I just installed a 3 SQL Server 2005 instances on a 2 node Active/Passive cluster. ... IWiz will then offer you a choice of Group on where you can install teh Fail Over Clustered Instance of SQL. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)
  • Re: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Server 2005 Cluster Setup Quiz
    ... I did test and it did not install the client tools. ... http://www.clusterhelp.com - Cluster Training ... Microsoft SQL Server MVP ... Provide a template on how to read SQL Server 2005 setup log files. ...
    (microsoft.public.sqlserver.clustering)