You should check sharepoint: library versioning, users recycle bin, second level recycle bin...

Last week we had the same problem this one our client, who turned on unlimited versioning in...

For sharepoint you should have SQL Server 2008 with SP1 and CU2. (or SP2). So just install patches.

If you want to run sharepoint on the same machine, make sure you...

I had the same problem on newly installed server. Try this hotfix which helped me http://support.microsoft.com/kb/976494

Also check your Active Directory Server is up

And also you can try to...

For sharepoint 2010 environment your sql server 2008 should be SP1 with CU2 at a minimum. SP2 is the best choise.

It is a case of just downloading and installing the...

redownload installation file: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8fbfc1de-d25e-4790-88b5-7dda1f1d4e17

Try to reboot server and then launch installation again.

Lowell is right. If you db grow cause transaction logs, configure maitenance plan to backup them every 15 min. This make trn log size under control.

Aslo you can check article:...

Run

restore filelistonly from disk='D:\SQLData\A.bak'

Watch results.

Is there logical names "A" and "A_log" or names is different?

Ups, I'm late with answer.... 🙂

As Yogeshwar Phull said, try:

"First of all u need to run, filelistonly to find out the logical file names:

restore filelistonly from disk='E:\A.bak' "

And then run your script

Try this:

RESTORE DATABASE B

FROM DISK = 'E:\A.bak'

WITH REPLACE, MOVE 'A_Data' TO 'E:\B.mdf', MOVE 'A_Log' TO 'E:\B_Log.ldf'

ALTER DATABASE B

MODIFY FILE (NAME = 'A_Data', NEWNAME = 'B_data')

GO

ALTER DATABASE B

MODIFY FILE...

Also check versioning in your sharepoint. Especially in libraries with large files.