Upgrading sql server

Hi Gurus,
Can anyone give me the same site where I can find MS SQL help like this one.
This is my problem. Apparently we've got an intranet server and it runs SQL2000 DB and we have bought the new one and we want to move the database from the old server to the new one then upgrade from SQL2000 - SQL2005 how do we go about doing this.
I know this is not a Microsoft forum but if there's anyone who can assist please help.
Thank you.

The first result returned from Google searching for the phrase 'upgrade SQL SErver 2000 2005' returned this: http://www.sqlservercentral.com/columnists/rpearl/installingandupgradingtosqlserver2005.asp
I have no idea if it's any use or not, but it says it's got the largest community of SQL Server users and there's a menu option for Discussion Forums, just like this one (one presumes!)

Similar Messages

  • Upgrade SQL server 2008 r2 to latest available Service Pack in SP 2010 farm.

    Hi, 
    We have 2 server's in the farm ( WFE+App server and SQL server).
    We are planning to upgrade SQL server 2008 r2 to latest available Service pack [10.50.6000 (SP3)] version.
    So before upgrading SQL server , need to take any necessary actions from SharePoint server side ?
    And once patching is done on SQL server, need to run SharePoint Configuration wizard ?
    Please provide best way for this upgrade.
    Cheers,
    RameshNK

    You certainly can turn off SharePoint/stop IIS if you wish, but it isn't required. SharePoint will be unavailable during a portion of the SP3 upgrade and will reconnect once SQL is back online.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Upgrade SQL Server 2000to SQL Server 2005 in an SAP environment

    Hi,
    I have a scenario in which we are going to upgrade SQL server 2000 to SQL server 2005 in SAP an environment.
    Now SQL server has a concept of In-Place Upgrade and Side-by-Side Migration Process.I want to know what does both of these mean.
    We have an SAP note(799058.It talks about the upgrade in Step II.Is it the same as In-Place Upgrade concept in SQL?
    What is step III in the note talking about? Is it talking about Side-by-Side Migration?
    It would be of gr8 help if someone could provide the conceptual knowledge on these and what does the note mentioned above talks.

    Hello
    Please review my post on SQL upgrade.
    SAP on SQL Server
    You may also like to review
    http://www.microsoft.ie/downloads/itprosql-90.ppt#568,17,Demo
    Can you please advise your DB size and the max. amount of downtime your business can afford?
    I will check, but I am almost sure that a side-by-side SQL upgrade is not appropriate for SAP systems.
    Thanks
    N.P.C

  • Limitations for upgrading SQL server database engin from SQL 2008 R2 enterprise edition to SQL 2014 enterprise edition

    Dear All,
    we are planning to upgrade  SQL Server 2008 R2 Enterprise edition to SQL Server 2014 Enterprise edition.
    please suggest the limitations for the up gradation.
    Thanks in Advance
    Vineet Srivastava
    NIIT Technology Ltd.
    New Delhi , India

    Hello,
    Please note that we have 2 Enterprise Editions now: 
    (1) Enterprise Edition with Server + Client Access License (CAL) and (2) the Enterprise Edition licensed by core. “Enterprise Edition with Server + Client Access License (CAL) based licensing (not available
    for new agreements) is limited to a maximum of 20 cores per SQL Server instance. There are no limits under the Core-based Server Licensing model”. Source:
    https://msdn.microsoft.com/en-us/library/ms143760(v=sql.120).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Upgrading SQL Server Questions

    Hi everyone.
    I've never upgraded SQL Server before, so I'm quite nervous (Maybe unnecessarily so?)...
    When I started development of the software we use here, another product required that we use SQL Server 2000.  That is no longer the case or an issue, so I wanted to upgrade SQL Server to a current version (That supports Windows Server 2003).  From
    my research, it looks like I would be able to upgrade to SQL Server 2008.
    I do have a few concerns though.
    1) Will my database function the same as it currently does?  Will my SQL Statements still work the same?  I haven't read anywhere where people were complaining of breaking changes, but I wanted to ask.  I would of course backup the database,
    but this database gets a lot of use, so I want to reduce headaches as best I can.
    2) How do I upgrade SQL Server?  I realize of course that this will be viewed as a ridiculously stupid question, but I genuinely have no idea and certainly don't want to botch that...
    3) Will this automatically upgrade all databases on the current server?
    4) Will I need to make any changes within my application, or will the upgrade be seamless from that aspect?
    5) Would I need to purchase anything for the upgrade?  I already have SQL Server as part of Visual Studio 2013...
    I really appreciate the help.

    Hello,
    1. In most cases normal upgrade works fine but if you are using a feature in you application that is not present in 2008 code might function differently.So testing is your best bet.In you case side by side upgrade would be best one
     2. Obtain new windows box and install SQL server 2008 on it.Migrate database from sql server 2000 to 2008 thorugh backup restore mechanism.Migrate logins and jobs as well by scripting it out and running it on 2008.RK on jobs and create script
    How to transfer logins
    Now test you application functionalities against this new database.See all works as expected if not change code accordingly.After you are confirmed that no app issue is there take full and trn saction log backup and restore it on 2008 and make it live
    dont decomission old 2000 let it be ther for 15 -20 days just in case.
    3. After you restore 2000 database backup on 2008 it will upgrade database automatically.You just need to change compatibility level to 100.
    alter database db_name set compatibility_level =100
    after this rebuild indexes and update stats for all tables and all databases.
    4. depends on issue if you face any speak to developer
    5 You need to have full version of SQL server installable.If you are planning to use express you can download from net.For standard /enterprise you need to have valid license
    Edit: As Olaf mentioned you need to run upgrade advisor as well ,even though it is required for inplace upgrade but that would be helpful, Still I would suggest for side by side approach
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Unable to upgrade SQL Server 2008 R2 to SQL Server 2012 SP1

    I'm encountering error after error, after successfully installing the upgrade advisor (which took some doing) and running it with essentially no warnings/errors (the one warning was on the connection strings, as I recall -- and all of the warnings had a
    "fix after" status.
    First failure involved SSRS and the inability to create the "managed account". Backed out the upgrade using http://sqldbanotes.blogspot.com/2013/10/how-to-fix-failed-in-place.html
    Now the failure involves SSAS and unable to connect to analysis services with name MSSQLServerOLAPService.  That is the logical name for the service, although it shows up as just MSSQLServer when looking at it in the services list.  I tried
    setting the service account to a local account as  well as to Local System -- did not make a difference, the upgrade couldn't apparently find it regardless.
    Has anybody successfully done an in place upgrade from SQL Server 2008 R2 to SQL Server 2012?

    Hi Bob，
    Thanks for your post and I am glad to hear that the issue is resolved. Thanks for you posting a reply to share your solution and I had marked it as answer. That way, other community members could benefit from your sharing.
    Regards,
    Sofiya Li
    If you have any feedback on our support, please click here.
    Sofiya Li
    TechNet Community Support

  • Upgrading SQL Server from 2008 to 2012 doesn't respect existing install / instance paths

    Basic Information : Running Microsoft Windows Server 2008 with MS SQL Server 2008 (version 10.0.5869), trying to upgrade to SQL Server 2012. Currently working in a cloned
    VM of our production server (so I can try things and not worry about affecting our production system).
    Current server setup:
    C Drive: Operating System (About 7 GB of 50 GB free)
    J Drive: Program Files (About 65 GB of 78 GB free)
    F Drive: SQL Databases (About 120 GB of 195 GB free)
    Issue: I am trying to do an upgrade of our existing MS SQL Server 2008 install. I am using the GUI method, and choosing "Upgrade from SQL Server, 2005, SQL Server
    2008, or SQL Server 2008 R2" in the Setup GUI:
    All the checks & rules run with no issues. When I get to the "Instance Configuration" screen in the setup GUI, it is not respecting where my SQL Server instance is already installed (which is on the J drive). Instead it wants to install EVERYTHING
    (including Instance Directory, which should be on the F drive, and the install folder, which should be on the J drive) on the C drive under C:\Program Files\ and there is no option in the GUI to change that, as it's grayed out.
    I tried using a Configuration File to do the upgrade, but when I tried to specify the specific paths, it says those variables are not allowed to be used in an upgrade. If I allow the install to go through, it seems to install fine, but only leaves me with about
    1.5 GB free on the OS drive (Drive C) and all of SQL Server is now installed on Drive C, which is not what I want or need.
    Looking in the Registry Editor, I can see that under HKLM\SOFTWARE\Microsoft\Microsoft
    SQL Server\MSQL11.MSSQLSERVER\ that the SqlProgramDir key
    has changed from "F:\" to "C:\Program Files\Microsoft SQL Server\" and that the SQLPath and SQLDataRoot have
    changed from "F:\MSSQL10.MSSQLSERVER\MSSQL" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL". SQLBinRoot has
    also been changed "F:\MSSQL10.MSSQLSERVER\MSSQL\Binn" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn".
    It doesn't seem to want to follow where the existing Install and Instance Directories are. Am I missing something here? I've done a decent amount of research, but can't find anything that talks about this. So I'm at a loss as to what to do from here.

    I haven't touched the registry. Here is the ConfigurationFile.ini from the original install (I've scrubbed sensitive info out of it) showing the paths:
    ;SQLSERVER2008 Configuration File
    [SQLSERVER2008]
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
    INSTANCEID="MSSQLSERVER"
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
    ACTION="Install"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
    FEATURES=SQLENGINE,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
    ; Displays the command line parameters usage
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console.
    INDICATEPROGRESS="False"
    ; Setup will not display any user interface.
    QUIET="False"
    ; Setup will display progress only without any user interaction.
    QUIETSIMPLE="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
    X86="False"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
    ERRORREPORTING="False"
    ; Specify the root installation directory for native shared components.
    INSTALLSHAREDDIR="J:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.
    INSTALLSHAREDWOWDIR="J:\Program Files (x86)\Microsoft SQL Server"
    ; Specify the installation directory.
    INSTANCEDIR="F:"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
    SQMREPORTING="False"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
    INSTANCENAME="MSSQLSERVER"
    ; Agent account name
    AGTSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Auto-start service after installation.
    AGTSVCSTARTUPTYPE="Automatic"
    ; Startup type for Integration Services.
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account.
    ISSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; The name of the account that the Analysis Services service runs under.
    ASSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Controls the service startup type setting after the service has been created.
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services.
    ASCOLLATION="Latin1_General_CI_AS"
    ; The location for the Analysis Services data files.
    ASDATADIR="F:\MSAS10.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files.
    ASLOGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files.
    ASBACKUPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files.
    ASTEMPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files.
    ASCONFIGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process.
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned.
    ASSYSADMINACCOUNTS=""
    ; Startup type for the SQL Server service.
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express.
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine.
    SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
    ; Account for SQL Server service: Domain\User or system account.
    SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Windows account(s) to provision as SQL Server system administrators.
    SQLSYSADMINACCOUNTS=""
    ; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication.
    SECURITYMODE="SQL"
    ; Provision current user as a Database Engine system administrator for SQL Server 2008 Express.
    ADDCURRENTUSERASSQLADMIN="False"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol.
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol.
    NPENABLED="0"
    ; Startup type for Browser Service.
    BROWSERSVCSTARTUPTYPE="Disabled"
    ; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
    RSSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Specifies how the startup mode of the report server NT service. When
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled
    RSSVCSTARTUPTYPE="Automatic"
    ; Specifies which mode report server is installed in.
    ; Default value: “FilesOnly”
    RSINSTALLMODE="DefaultNativeMode"

  • Upgrading SQL Server 7.0 to SQL Server 2000

    Hello,
    We want to upgrade Microsoft SQL Server 7.0 to SQL Server 2000 to implement Mobile scenario in CRM .If anyone has any utility  implementation guide or good information regarding it ,kindly please forward it to my mail id  [email protected]
    Thanks and Regards,
    Saumya Maheshwari

    Hello Saumya,
    I have sent you a Upgrade note. Hope that will be of help. However, I like to tell you that there is no migration procedure, per se. But you could follow the steps in the document and it should be a straight forward approach to 2000.
    In case,the authentification of the SQL Server 7.0 is set to "Windows NT only";While upgrading, the user chooses "The SQL Server system administrator login information (SQL Server authentication)" in the "Connect to Server" step and enters the password for the system administrator (sa).
    In the next step, the upgrade program checks if the user can log on to SQL Server. First, the Windows authentification of the logged on user is checked, which is successful. The 'sa' user and the relevant password are not verified. However, later in the upgrade process, the program tries to execute the scripts with the 'sa' user; this fails due to the "Windows NT only" authentification for SQL Server. The error ("Error running script: upgrade.sql(1)") message is written to the log file (upgrade.out) of the script (upgrade.sql):
    Login failed for user 'sa'. Reason: Not associated with a trusted SQL
    Solution - The upgrade program of SQL Server 2000 saves the settings of the upgrade in the registry. You can change the authentification mode there. Start the registry editor and go to the following entry in the left panel:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Setup\Resume\
    Locate the "DO-NT" value in the right panel. Change this value from "0" (SQL Server authentification) to "1" (NT authentification). You can then restart the upgrade; the program now logs on to SQL Server via the Windows authenification and also executes the scripts under this authentification.
    Please award points in case you find the solution of help to you.
    Thanks
    Sumit

  • Upgrade SQL Server 2008 R2 enterprise edition to SQL server 2012 slandered edition

    Hi everyone,
    Need help on below concern.
    I have SQL Server 2008 R2 enterprise edition installed. Which contains SSAS cubes, SSIS packages and SSRS Reports. 
    I need to upgrade it to SQL Server 2012 Standard edition. 
    How can I achieve this ??
    And I don't have much idea in SSIS package migrations. 
    Please help me to achieve this. 
    Thanks,
    Rohit

    Hi,
    Please follow side by side approach for upgrade.Get a new windows box and install SQL server 2012 on it
    Move databases from SS2008 R2 to SS 2012 by backup restore mechanism.
    Move
    jobs and logins by Scripting out and running it on SQL SS 2012.See links as well
    Please refer to
    this link for SSIS package migration
    For SSAS please post question in SSAS forum
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • Upgrade sql server 2008 to 2008R2 and apply Service pack 3

    Hello,
    I have a two node cluster (sql server 2008).  I would like to upgrade to SQL Server R2 and at the same time would like to patch to Service Pack 3.  What would be the best way to accomplish this task with minimal downtime to the users?
    This is my plan:
    1.  Detach any read only databases.
    2.  Upgrade to 2008 R2 (shared feature only) on passive node (node1).
    3.  Apply SP3 on passive node in step 2.
    4.  Swith active node to passive node (node2).
    5. Upgrade to 2008 R2 (shared feature only) on node2.
    6. Apply SP3 on node2.
    7.  Upgrade db (instance) on node2 to 2008 R2.
    8.  Upgrade db (instance) on node1 to 2008 R2.
    9.  Re-attach read only databases.
    Is my procedures correct?
    Thank you.

    Hello,
    Have you seen the following article before?
    http://msdn.microsoft.com/en-us/library/ms191295(v=sql.105).aspx
    You can slipstream SQL 2008 R2 + SP3.
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • How to upgrade SQL Server 2012 SSMS

    I have SQL Server 2012 SSMS (11.0.3000.0) on my machine, however this crashes at least 5-8 times a day. So I want to try to apply KB2874879. But when I try to install it I can't progress because it says there is no instance found to apply. I only want
    to update the SSMS, I'm not running any local instance on that machine. How can I get SSMS to the latest version ?

    Hi,
    According to your description, I know the SQL Server Management Studio always crashes on the client machine and there is no SQL Server was installed on that machine.
    KB2874879 is cumulative update package 6 for Microsoft SQL Server 2012 Service Pack 1 and it should be installed on SQL Server. And install CU6 does not guarantee it will resolve the SQL Server Management Studio crash issue on the client machine. If the
    SQL Server Management Studio is corrupted, you need to perform a repair installation from the Installation Center.
    Thanks.
    Tracy Cai
    TechNet Community Support

  • Upgrade SQL server to increase processing speed

    I have connected SQL server to my web service and currently the number of records being processed by a particular table has increased on a large scale. As a result of deleting and inserting into this table, the performance has gone down. Are there any
    suggestions on how existing SQL server can be updated to increase the performance? Currently im using SQL server Enterprise edition 2012. Only a single server is been used with no replications. Please advice.
    mayooran99

    Hi
    First of all, check out for fragmentation due to massive insert/delete operation an index is out of order
    SELECT avg_fragmentation_in_percent FROM sys.dm_db_index_physical_stats
      DB_ID('testdb'),
      OBJECT_ID('dbo.T1'),
      1,
      NULL,
      NULL
    What does the above return?
    To rebuild index/es
    --single index
    ALTER INDEX IX_Str ON tblname
    REBUILD;
    GO
    --all indexes on the table
    ALTER INDEX ALL ON tblname
    REBUILD WITH (FILLFACTOR = 80, SORT_IN_TEMPDB = ON,
                  STATISTICS_NORECOMPUTE = ON);
    GO
    More over to speed up the query you need to have properly defined indexes on the table.
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Upgrade sql server 2008 to 2014

    Hello,
    1- is it possible to install 2014 while 2008 is installed. And then restore the 2008 database into the 2014 version?
    2- is 2014 version out and can it be fully used now?
    Thanks

    SQL Server edition
    Definition
    Enterprise (64-bit and 32-bit)
    The premium offering, SQL Server 2014 Enterprise edition delivers comprehensive high-end datacenter capabilities with blazing-fast performance, unlimited virtualization, and end-to-end business intelligence — enabling
    high service levels for mission-critical workloads and end user access to data insights.
    https://msdn.microsoft.com/en-us/library/ms144275.aspx
    SQL Server Data Tools - Business
    Intelligence (SSDT-BI) includes SQL Server Analysis Service Projects, SQL Server Reporting Services
    Projects, and SQL Server Integration Services Projects hosted in Visual Studio. SSDT-BI
    tools can be downloaded and installed as free tools from the web.
    http://blogs.technet.com/b/dataplatforminsider/archive/2013/11/13/microsoft-sql-server-data-tools-update.aspx

  • SSIS packages are failing after upgrade to SQL server 2014

    Hi,
    I have some SSIS packages running on SQL server 2012 .
    After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
    And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
    I read some articles about this and they say it not able to connect to SQL server agent job.
    And, I can see that the package is running if i run manually using SQL 2012 run time.
    Why its not running on SQL 2014 ?
    did i  miss anything while upgrading SQL server 2014 ?
    Please give me some suggestions to solve this issue. 
    And is there any way i can change the SQL server agent 2014 to adapt this and run ?
    Below is the error : 
    The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
    errors.: This occures when CPackage::LoadFormXML fails.
    Regards,
    Vinodh Selvaraj.

    I think you have typed this error message by yourself.
    Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
    If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
    You may try executing package in 32 bit mode from SQL Agent Job.
    Please refer:
    http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
    http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
    -Vaibhav Chaudhari

  • Upgrade from sql Server 9.0 to sql Server 12.0

    I am currently running SQLEXPRESS (SQL Server 9.0)  It appears that there is a limit to the size of the database which I have exceeded.  I want to restore a backup of my customers DB and am not allowed to do so.  Appears to be a size issue,
    the customer DB is over 5 GB.
    Will I eliminate this size restriction using sql Server 12.0?
    I don't see any references to upgrading sql Server 9.0 to sql Server 12.0, only references to a new installation.  Can it be upgraded and how do I do that?

    Hello,
    Please read the following article.
    http://www.mssqltips.com/sqlservertip/2941/upgrading-to-sql-server-2012-express
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

Maybe you are looking for