Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / July 2008

Tip: Looking for answers? Try searching our database.

SQL Server 2005 is screwing up my SharePoint backups?!

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Conrad Goodman - 10 Jul 2008 10:39 GMT
I have SQL Server 2005 and SharePoint Server 2007 installed on a single box.

The problem I am having is with SharePoint backups, they fail claiming that
another tool carried out the last back up.

It appears that at 10PM every night, SQL Server backs itself up some how.

I am a complete newbie to SQL Server, I've literally just installed it and
let it sit there.

Is there a default backup schedule I can modify to prevent this from
happening?

Thanks

Conrad
Tibor Karaszi - 10 Jul 2008 10:54 GMT
> It appears that at 10PM every night, SQL Server backs itself up some how.

Not by default.

> Is there a default backup schedule I can modify to prevent this from happening?

No. Check if you have any SQL Server Agent jobs, and if so any of those do this backup. If not, then
this happens from outside your SQL Server.

Signature

Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi

>I have SQL Server 2005 and SharePoint Server 2007 installed on a single box.
>
[quoted text clipped - 10 lines]
>
> Conrad
Uri Dimant - 10 Jul 2008 11:00 GMT
Conrad
You can create a maintanence task to backup all user databases or using
T-SQL BACKUP DATABASE commamd traverse trou all user database.
Im my experience , running SQL Server production along with SharePoint is
one big mistake. In terms of databases SP is disaster that hits performance
and its databases heavily involved in deadlocks  which I'm not able to fix
http://dimantdatabasesolutions.blogspot.com/2008/06/how-do-you-maintain-sharepoi
nt.html


>I have SQL Server 2005 and SharePoint Server 2007 installed on a single
>box.
[quoted text clipped - 13 lines]
>
> Conrad
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.