Microsoft sql server ошибка 1827

I’m attempting to extract data from a SQL Server backup provided by vendors with whom we no longer work.

I only need data from some tables, but I need to examine the database structure to determine exactly what I need.

This is the only use I have for SQL Server and I don’t what to buy in big.

I tried SQL Server Express to restore the .bak file locally and received the error:

Restore failed…
CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.
RESTORE DATABASE is terminating abnormally. (Microsoft SQL Server, Error: 1827)

I am having difficulty determining what alternative approach or minimum license I need to purchase to get me past this database size limit. The database seems to be only marginally over the limit.

I used RESTORE FILELISTONLY, HEADERONLY and LABELONLY commands to extract what metadata I could.

HEADERONLY
BackupSize: 4958099456

I’m running SQL Server Express 2008 on a Win XP 32 bit platform, which could be part of my problem.

The version I’m running:

Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (Intel X86)  
Sep 22 2011 00:28:06  
Copyright (c) 1988-2008 Microsoft Corporation  
Express Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)

Can anyone tell me the least expensive and most efficient way out of this problem?

Thanks,
Neale

• Either shrink your database or upgrade to a full copy of SQL.

  As the error says:

   the resulting cumulative database size would exceed your licensed limit of 4096 MB per DB».

  ,

  You are limited to a 4GB database size with SQL express. You are close to breaching that.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Rockn

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  mace

  Using SQL Express for Sharepoint was your first mistake as it doesn’t scale well. Purchase a full version of SQL Server and move the db over if possible.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Thanks Gary, I already, shrinked the DB. but now much affective.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Upgrade your ‘SQL server’. Safest path to go on.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Rockn, 

  Thanks, i guess i have the only option to purchase enterprise unlimited version. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Standard SQL will also work in this scenario.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Another option is to upgrade to a newer version of Express (if you environment will allow/support it).  MSSQL 2012 Express allows up to a 10 GB Db size.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• LincolnITGuy wrote:

  Another option is to upgrade to a newer version of Express.  MSSQL 2012 Express allows up to a 10 GB Db size.

  Correct. But it looks like some audit table is running out of space. So the 2012 Express would probably also fail in the near future.

  This is a guestimate from my side I know.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Thanks, Oscar4000,

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  This is true, good point Oscar.  

  No matter what, any express installation is going to be a temporary solution when used as a SharePoint back-end.  As Rockn said above, it inherently doesn’t scale well. I used it on our initial vSphere vCenter installation and that filled up after a couple years.  Learning from my mistake, my philosophy is now no express unless it is a test/lab setup (or for a home/hobby/school type project).

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Fellows,

  Please assist me. In case of

  1. Backup successfully processed from Central administration sharepoint.

  2. Uninstall sql server 2005 and all updates. 

  3, sql server 2014 install from scratch.

  4. restore the sharepoint. 

  In above actions, please advise, sharepoint will be work fine after restoration. or I have the only option to upgrade from 2005 to 2014. Because still I didn’t work with sql server 2014.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Why not install sql 2014 on another vm?

  This way you can backup and restore the share point db and, if it doesn’t work you have a rollback plan.

  
  Was this post helpful?
  thumb_up
  thumb_down