Re: SQL 2005 Embedded and Moving Sharepoint Services Database



Hi,

Why are you moving the log file off the C drive? If you're moving it
because it has grown too large and you're running out of space then you're
going about things the wrong way. That file will keep growing if you're
running your database in FULL or BULK_LOGGED recovery mode and eventually no
matter where you place it you'll keep running out of space. What you need
to do is to (regularly) run a backup of the log then shrink the file to a
size that make sense for your environment (something that avoids a lot of
growth operations). So if you connect via osql run something as follows:

backup log mydb
to disk = 'c:\mybackuppath\mybackupfile.bak'
go

use mydb
go

dbcc shrinkfile (mylargelogfile, 500)


Jonathan


"Watt, Bobby" <xp1les@xxxxxxx> wrote in message
news:3DE82A96-888E-4307-95F9-23EF23C473DB@xxxxxxxxxxxxxxxx
I have a SQL 2005 Embedded database that was created by SharePoint
Services. It's ldf file has grown to almost 3 gig, and I need to move it
off the C drive. I have successfully moved some of the other databases
using the OSQL command, but when I try to move this one particular database
I keep getting a syntax error. I've checked and rechecked the file name and
I'm typing it in right. It's the Sharepoint_Config database.

SharePoint_Config_0e211848-1a2a-47d8-a407-ec9839afe12b.mdf

The error states Incorrect Syntax near '-'.



Couple of questions.

How can I connect to this database using the SQL 2005 Management Studio?
I'm connecting to CYAN\MICROSOFT##SSEE and using Windows Authentication.

This is the error I get.


Cannot connect to CYAN\MICROSOFT##SSEE.

===================================

An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (.Net SqlClient Data Provider)

Any suggestions would be appreciated.



.



Relevant Pages

  • Re: Access 97 to a more powerfull platform!?
    ... Moving to SQL Server is common when a database "outgrows" ... Design problems are far and away the usual reason why a database ...
    (microsoft.public.access.gettingstarted)
  • Re: Help! Cant connect via ODBC DSN file to SQL server 2005 if not considered a default database
    ... ODBC, just the original database. ... you connect to a SQL Server ... connecting to SQL Server. ... connecting to allows you to install a training or release version of the ...
    (microsoft.public.sqlserver.odbc)
  • Re: Cant read from database ??
    ... You also may need to worry about some permissions. ... http://msdn2.microsoft.com/en-us/library/ms345408.aspx Moving ... Issues When a Database Is Moved Between SQL Servers ... for SQL Server ...
    (microsoft.public.sqlserver.connect)
  • Re: Replication Problem
    ... > context on connecting to the distributor database. ... and could not access my SQL Server - when I tried ... > Another thing to try is to create a subscription database via Enterprise ... > Manager and see if you get the error about connecting to the Distributor. ...
    (microsoft.public.pocketpc.developer)
  • Re: Replication Problem
    ... > context on connecting to the distributor database. ... and could not access my SQL Server - when I tried ... > Another thing to try is to create a subscription database via Enterprise ... > Manager and see if you get the error about connecting to the Distributor. ...
    (microsoft.public.sqlserver.ce)