Backup/restore across Enterprise & Standard Editions?

With the exception of incremental backups, are there any impediments to backing up from an Enterprise & restoring in a Standard edition??

The restores via RMAN from EE to Standard should just work. Limitiation of the RMAN Standard edition are:
Parallelization
Duplexed backups
TSPITR via RMAN
Incrementals
The other issue that you have to be concerned with is the features and functions that you have implemented in the EE version vs. the Standard version of the database.
Thanks, Tammy

Similar Messages

  • Partition option for Oracle 9i Enterprise/Standard Edition

    Hello All,
    could you help me please.
    I'd like to download Oracle9i Database Release 2 Enterprise/Standard Edition for HP 9000 Series HP-UX for demonstration purposes.
    Tell me please does it mean that this Enterprise Edition includs Partition option?

    Installing Oracle is not easy for the beginner. Please consider asking Oracle Sales to assist you, as they have technical consultants who can do that for free.
    All Oracle software that can be downloaded if available from http://otn.oracle.com ... look for the Downloads link at the top.
    Partitioning Option is included in the Enterprise Edition software, but using Partitioning Option requires purchasing a separate license for the option. It can NOT be licensed for use with the Standard Edition.

  • Retore a backup from RAC to Standard Edition

    Hi,
    We have a production environment with a 2 nodes RAC 11g.
    This environment is secured with a RMAN backup startegy.
    Could we restore the backup to a single node Oracle Standard Edition 11g database?
    Best regards,
    Sébastien

    So I would be careful, this metalink has a list of differences between EE and SE:
    Differences Between Enterprise, Standard and Personal Editions on Oracle 11.1
    Doc ID: NOTE:465460.1
    If you use EE options and features, you cannot have these in the restored SE instance.
    Werner

  • RMAN backup, restore across different versions

    OS : Solaris 10
    I have an RDBMS software only installation of 11.2.0.3 in a server ---> Server B
    I have my source DB running on another server which is of version 11.2.0.1.0 -----> Server A
    Is it possible to take RMAN backup of the source DB of version 11.2.0.1.0 and use it create a DB of 11.2.0.3.0 in server B ?
    Is the same possible for 10.2.0.1.0 to 11.2.0.3.0 ?

    I believe its this
    alter database open resetlogs upgrade;The startup has to be either MOUNT or NOMOUNT ( double checking )
    Create a spfile and then
    SQL*Plus: Release 11.2.0.3.0 Production on Fri Jul 13 15:33:24 2012
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Connected to an idle instance.
    SQL> startup nomounth2. Super example
    See Levi Pereira's post here :
    alter database open resetlogs upgrade ;         throwing error
    Best Regards
    mseberg
    Edited by: mseberg on Jul 25, 2012 10:18 AM

  • Enterprise verses Standard Edition

    Hi All,
    What is the difference between Oracle 10gAS Enterprise & Standard Editions?
    Thanks.

    From the SQL Server installation guide:
    ● SQL Server 2000/2005: Enterprise and Standard Edition
    ● SQL Server 2008: Enterprise (capture or delivery) or Standard Edition (delivery only)
    ● SQL Server 2008 R2: Enterprise (capture or delivery) or Standard Edition (delivery only)

  • Best procedure to downgrade a SQL Server 2012 SP2 installation from Enterprise edition to Standard edition

    Hi,
    following a purpose change for a database server, I need to downgrade the SQL Server 2012 SP 2 installation from Enterprise to Standard edition.
    Does it exist the best procedure to do it in a secure manner with a low impact?
    Many thanks

    Please note that while you are downgrading by uninstalling and reinstalling and then restoring backup  taken from 2012 enterprise to standard , if backup contains data about used enterprise features you would not be able to restore the backup so BE
    CAREFUL.
    You should , if possible, get a new box install SQL Server standard and try restoring backup if it fails disable enterprise features and again take backup and then you would be able to restore.
    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 Article
    MVP

  • Migration SAP SolMan 7.1 MSSQL 2008 R2 Enterprise Edition to MSSQL Standard Edition

    Hello,
    I try to migrate a SAP SolMan 7.1 on Windows MSSQL 2008 R2 ENTERPRISE EDITION to
    MSSQL 2008 R2 STANDARD EDITION.
    In the source system (MSSQL 2008 R2 ENTERPRISE EDITION) there is "table compression" and
    "partitioning" active.
    the MSSQL STANDARD EDITION doesn`t support these two features.
    So a normal DB backup on the source system and restore in the destination system is not possible.
    But the tables compression I can deactivte by the SQL script
    SELECT DISTINCT ‘ALTER TABLE [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
    FROM sys.partitions p
    join sys.objects o
    on p.object_id = o.object_id
    WHERE o.TYPE = ‘u’
    and data_compression_desc != ‘NONE’
    UNION
    SELECT ‘ALTER INDEX ALL ON [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
    FROM sys.partitions p
    join sys.objects o
    on p.object_id = o.object_id
    WHERE o.TYPE = ‘u’
    and data_compression_desc != ‘NONE’
    is there a way to undo or deactivate the the SQL table partitioning without any data lost ?
    Or is there a other way to migrate a SAP SolMan 7.1 form MSSQL 2008 R2 ENTERPRISE EDITION to MSSQL 2008 R2 STANDARD EDITION ?
    Best regards
    A. Moore

    Hi Moore
    Could you refer the SAP Note for MS Sql Version supports
    1076022 - Release planning for Microsoft SQL Server 2008 (R2)
    and MS SQL table compression & decompression SAP Note
    1488135 - Database compression for SQL Server
    BR
    SS

  • Upgrading from Oracle 9i Standard edition to Enterprise.

    I want to upgrade my database from oracle 9i(9.2.0.6) Standard edition to Enterprise edition.
    Please suggest me as to what is the best suitable method
    I was thinking of installing EE directly on Standard edition so that all the things remain intact is it possible?
    Also if not then can backup and restore be used?
    Thanks in advance

    hi.
    right now i have standard edition already installed as i said earlier. I want to upgrade from SE to EE because of using advance features like partitioning. DB size is 40 GB.
    I know exp/imp would take a lot of time that's why I thought it is not a viable path.
    regards,
    pranav

  • Backup Encryption in SQL Server Standard Edition

    Hello,
    I need experts advice on Backup encryption options available in SQL Server 2008 R2 Standard Edition. I know TDE is available, but only in Sql Server 2008 R2 Enterprise edition. But we are using Standard Edition.
    Thanks

    Password protect is not the same thing as encryption - the data is still clear text. This is what Books Online for SQL Server 2008 say about the password option:
    "The protection provided by this password is weak. It is intended to prevent an incorrect restore using SQL Server tools by authorized or unauthorized users. It does not prevent the reading of the backup data by another method or the replacement of the password.
    This feature will be removed in the next version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. "
    And in 2012 this option is indeed removed from the backup command.
    Tibor Karaszi, SQL Server MVP |
    web | blog

  • Downgrade SQL Server Enterprise Edition to Standard Edition

    Hi
    I came to know in-place edition downgarde from SQL Server Enterprise to SQL Server Standard edition is not possible after seeing couple of questions in the forum, But I find one interesting article in the web which says in-place downgrade is possible and
    I tried the same and it works for me, below are the steps
    1.    Type regedit.msc
    2.    Got to SQL installation section in registry by default it will be here:
     HKLM(HKEY_LOCAL_MACHINE) -> SOFTWARE -> Microsoft -> Microsoft SQL Server ->
    3.    Here you have to select the instance you want to downgrade if you have multiple instances.
    Expand required instance folder.
    MSSQL10_50.MSSQLServer -> Setup
    4.    Click on ‘Setup’
    5.    Here You need to change one by one all below entries.
    AGTGroup
    DigitalProductID
    Edition
    EditionType
    ProductCode
    ProductID
    SQLGroup
    FDHostGroup
    Checksum
    Take these values from any already installed Standard edition instance and replace here.
    Make sure from where you are taking these values have the same features installed and same version and all.
    6.    Now click on ‘SQL_Engine_Core_Inst’ and change the entries here as well.
             ProductCode
    But I am not sure how reliable is that option, Could someone let me know can I use that process for downgrade
    Regards
    calyan
    Kalyan Akula

    Hi,
    I would ceratinly not do that If I were you, this would surely leave you in unsupported state. You should ask Microsoft whether tweaking registry and replacing just value can actually change enterprise to standard or whether it is supported or not. I guess
    you are just fooling the system.
    Its better to uninstall Enterprise edition and Install Standard edition and create database using backup restore or attch detach.
    I have not tried what you have mentioned. But thank you for the information.
    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

  • Migration SAP SolMan 7 MSSQL 2008 R2 Enterprise Edition to MSSQL Standard Edition

    Hello,
    I try to migrate a databse on Windows MSSQL 2008 R2 ENTERPRISE EDITION to
    MSSQL 2008 R2 STANDARD EDITION.
    In the source system (MSSQL 2008 R2 ENTERPRISE EDITION) there is "table compression" and
    "partitioning" active.
    Unfortunately the MSSQL STANDARD EDITION doesn`t support these two features.
    So a normal DB backup on the source system and restore in the destination system is not possible.
    But the tables compression I can deactivte by the SQL script
    SELECT DISTINCT ‘ALTER TABLE [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
    FROM sys.partitions p
    join sys.objects o
    on p.object_id = o.object_id
    WHERE o.TYPE = ‘u’
    and data_compression_desc != ‘NONE’
    UNION
    SELECT ‘ALTER INDEX ALL ON [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
    FROM sys.partitions p
    join sys.objects o
    on p.object_id = o.object_id
    WHERE o.TYPE = ‘u’
    and data_compression_desc != ‘NONE’
    is there a way to undo or deactivate the the SQL table partitioning without data lost ?
    Best regards
    B.-D.

    Hello Lydia Zhang,
    thanks for your help.
    For a few tables this will work.
    Unfortunately I have an SAP system with thousands of tables and index`s .
    With the SQL script:
    SELECT
     SCHEMA_NAME(t.schema_id) AS SchemaName
    ,OBJECT_NAME(i.object_id) AS ObjectName
    ,p.partition_number AS PartitionNumber
    ,fg.name AS Filegroup_Name
    ,rows AS 'Rows'
    ,au.total_pages AS 'TotalDataPages'
    ,CASE boundary_value_on_right
        WHEN 1 THEN 'less than'
        ELSE 'less than or equal to'
     END AS 'Comparison'
    ,value AS 'ComparisonValue'
    ,p.data_compression_desc AS 'DataCompression'
    ,p.partition_id
    FROM sys.partitions p
    JOIN sys.indexes i ON p.object_id = i.object_id AND p.index_id = i.index_id
    JOIN sys.partition_schemes ps ON ps.data_space_id = i.data_space_id
    JOIN sys.partition_functions f ON f.function_id = ps.function_id
    LEFT JOIN sys.partition_range_values rv ON f.function_id = rv.function_id AND p.partition_number = rv.boundary_id
    JOIN sys.destination_data_spaces dds ON dds.partition_scheme_id = ps.data_space_id AND dds.destination_id = p.partition_number
    JOIN sys.filegroups fg ON dds.data_space_id = fg.data_space_id
    JOIN (SELECT container_id, sum(total_pages) as total_pages
            FROM sys.allocation_units
            GROUP BY container_id) AS au ON au.container_id = p.partition_id
    JOIN sys.tables t ON p.object_id = t.object_id
    WHERE i.index_id < 2
    ORDER BY ObjectName,p.partition_number;
    GO
    Output:
    SchemaName    ObjectName    PartitionNumber    Filegroup_Name    Rows    TotalDataPages    Comparison    ComparisonValue    DataCompression  
     partition_id
    swp    /BI0/F0CCMARSH    1    PRIMARY    0    0    less than    NULL    NONE    72057613126729728
    swp    /BI0/F0CCMAWDD1    1    PRIMARY    0    0    less than    NULL    NONE    72057613127516160
    swp    /BI0/F0CCMAWDD2    1    PRIMARY    0    0    less than    NULL    NONE    72057613128237056
    swp    /BI0/F0CCMAWDH1    1    PRIMARY    0    0    less than    NULL    NONE    72057613128957952
    and so on
    I got about 5000 tables .
    Is there a way to delete all index on the partioned table an create a new with one script ?
    Best regards
    B.-D.

  • Migration from Enterprise edition to Standard Edition

    Hi,
    DB version :10.2.0.4 (production database)
    OS version :windows 2003 Std edition 64 bit.
    how to migrate database from enterprise edition to standard edition.
    1)cold backup will be sufficient?
    or any way to migrate with best way> will be any impact after migrating.
    will be appreciated fro right answers.
    Thanks

    hi sb,
    Thanks for your response.
    1)i did clone database from enterprise edition to standard edition, no invalid objects found ( from production to development)
    2) i did restoration using RMAN backupsets from ENterprise edition to standard edition , no invalid objects found (from production to development)
    3) i did cold backup from enterprise edition to standard edition , no invalid objects found ( test machine)
    i already checked this before, but here mentioned as to use traditional export / import instead of expdp/impdp. ?
    Thanks

  • Downgrade SQL Server 2008 Enterprise to SQL Server2008 Standard Edition

    I would like to know from fourm users, what are the necessary steps I would take care for above mentioned activity and also please let me know best suitable option for Production.
    SNS

    You can't do in-place downgrade. You need to go with backup -> uninstall ent -> install std -> bring it to same patch -> restore databases approach.
    You need to make sure that there is not enterprise only feature used else you can't restore database on standard.
    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    Balmukund's answer above is the Microsoft supported route for doing a downgrade of an instance of SQL Server.  However, before you do this, you need to query the sys.dm_db_persisted_sku_fearures DMV in each of your user databases to make certain that
    you don't have any Enterprise features in use that would block your ability to restore a database onto Standard Edition.
    No matter what you are going to have to do an uninstall and reinstall of the SQL Server instance to downgrade the SKU.  However, you can save yourself some time and the headache of trying to restore the system databases if you are careful about what
    you do.  I have done a couple of SKU downgrades in the past and the easiest way to do it, and I am not saying this is the Microsoft supported way but that it works if done correctly, is to:
    Take a good backup of all of your databases (system and user).  
    Run SELECT @@VERSION and note the specific build number of SQL Server that you are currently on.
    Shut down your existing instance of SQL Server.  
    Copy the master, model, and msdb database files (both mdf and ldf), don't move them copy them, from the current location to a new folder that you mark as readonly. 
    Uninstall SQL Server from the system.
    Reboot the server.
    Install SQL Server Standard Edition.
    Apply the necessary Service Pack and/or Cumulative Updates to bring the instance up to your previous build number.
    Shutdown SQL Server.
    Copy the master, model, and msdb database files (both mdf and ldf) from the folder you saved them in to the correct location for the new install and remove the readonly flag from the files, and change the file ACL's so that the SQL Service account has Full
    Control over the files.
    Startup SQL Server and if you did it correctly it will startup and be exactly where you were before you made any changes, with all of your user databaes online and you should be ready to let applications connect and resume operations.
    If you screw something up in the above, you still have your backups and you can run setup to rebuild the system databases and then go about following the Microsoft supported path for restoring the system databases and then user databases into the system
    to bring it online.  Essentially the file copy is no different that what would occur through attach/detach you are just doing it with system databases which is not supported, but it does work.  The key is to have your backups from before you do anything
    so you have the supported route available if you encounter an issue.  The only issue I have ever had doing this set of steps is that I didn't set the file ACL's correctly and the database engine threw Access Denied errors and failed to start until I fixed
    the ACL's correctly.  This can save you many hours of frustration and downtime trying to restore everything since the database files are already there and it is just some small copy operations to put them where you need them to be.
    Balmukund, feel free to beat me over the head for suggesting a non-supported path. :-)
    Jonathan Kehayias | Senior Consultant,
    SQLSkills.com
    SQL Server MVP | Microsoft Certified Master: SQL Server 2008
    Feel free to contact me through
    My Blog or
    Twitter. Become a
    SQLskills Insider!
    Please click the Mark as Answer button if a post solves your problem!

  • Upgrade BizTalk 2013 Standard Edition to Enterprise edition

    Hi All,
    I wanted to upgrade from BizTalk 2013 Standard Edition to BizTalk 2013 Enterprise edition. Could you please let me know the steps that I need to follow or the point me to any related documentation.
    Thanks and Regards,
    Ujjwal
    -Ujjwal

    Back-up of databases
    BizTalk application.
    Backup the binding, parties, policies, vocabularies.
    BTSNTSVC.config file.
    Backup the Enterprise Single Sign-On secret
    This would help you if in case of any rollback
    When run the installation package for
    Enterprise edition, the install will detect
    the exiting version and guide you to upgrade. The install will also ensure the
    installed BizTalk application is not be affected.
    Use the back-ups if anything goes wrong. 
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Lync Standard Edition Servers - paired across datacenters question

    Hi all
    I am designing a Lync deployment for a small org (circa 800 users) obviously they keep banging on about HA/resiliency etc
    my initial design was a pair of standard edition servers in a single (tier 3) datacentre (with dual edge servers), they keep insisting they require a 50/50 split across a second datacenter
    so obviously with Enterprise Edition it is possible to have a high degree of resiliency both in and between datacenters - but at some cost and with massive server bloat - seems over engineered
    and if you do it with SE server - I,e split the SE server between datacenters you loose any resiliency in each datacentre - and presumably if a server needs maintenance etc then you need to fail over the entire userbase from one datacentre to the other
    what are people views on this - I still think the paired SE topology in a single datacentre is the best compromise (the WAN with be fully resilient too)
    do I have any other options

    Keep in mind, pool pairing isn't HA and it's not automatic, it's just a level of resiliency.  If one server needed maintenance, you'd still want to plan downtime to manually fail the users over so they didn't see the blip. 
    The large benefit to running the pair in the same site where all the users live in that site would mostly just be the WAN access.  Two party audio/video chats will generally send the media directly between the endpoints, so that wouldn't necessarily
    cross the WAN anyway. IM traffic is pretty negligible, but would hit the front ends and if you're strapped for WAN bandwidth you may want to watch it. More so, if someone on the far end datacenter scheduled a conference for users in the main datacenter with
    video, then you could have heavy traffic hitting the WAN to get to the other site and back.
    The big benefit to putting it in a different datacenter is of course simply site resiliency. 
    The difference between a full datacenter failover and a failover in the same site isn't that different with pool pairing however, in both cases it's a handful of PowerShell commands and in a pinch some quick DNS and topology changes.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

Maybe you are looking for