WIndows 2012 Essentials & SQL Server 2012 Standard

Does anyone know if SQL 2012 Standard (preferred) or 2008 can be installed on Windows Server 2012 Essentials? We're a small business with 10+ active users and have a need to upgrade our legacy inventory/CRM database to a new solution that requires SQL
Server. With such a small user base I don't foresee an impact. Are there any implications to installing SQL on Essentials?
Thank you

Hi SmallBizUser,
Just that it is not recommended to install SQL Server on a domain controller. There are specific security restrictions
when running SQL Server in this configuration and given the resource demands of a domain controller, SQL Server performance may be degraded. There are more details in the following KB. Please refer to.
You may encounter problems when installing SQL Server
on a domain controller
Meanwhile, please also refer to the following similar thread.
SQL
on Server 2012 Essentials
Hope this helps.
Best regards,
Justin Gu

Similar Messages

  • Windows Server 2012 Essentials and Microsoft SQL Server 2014 Standard Core Edition

    Our company is planning to buy Windows Server 2012 R2 Essentials edition (Volume license) and install it on Citrix Xenserver based virtual machine with 4 virtual processor cores. Can we install Microsoft SQL Server 2014 Standard Core Edition (2 licenses
    for 2 cores) and run it on this virtual machine?

    you can install SQL Server Standard 2014/2012 on the Essentials Windows Server but without Server core Installation while installing SQL Server 2014 is supported on the Server Core mode of the following editions of Windows Server:
    Windows Server 2012 R2 Datacenter 64-bit
    Windows Server 2012 R2 Standard 64-bit
    Windows Server 2012 Datacenter 64-bit
    Windows Server 2012 Standard 64-bit
    Windows Server 2008 R2 SP1 Datacenter 64-bit
    Windows Server 2008 R2 SP1 Enterprise 64-bit
    Windows Server 2008 R2 SP1 Standard 64-bit
    Windows Server 2008 R2 SP1 Web 64-bit
    http://msdn.microsoft.com/en-us/library/ms143506.aspx
    thanks
    diramoh
     

  • Write access to a directory for ASP 2.0 application stops working on Windows 2012 Standard Cloud Server

    Just moved our ASP 2.0 based web application to a Windows 2012 Standard Cloud Server.  A directory is used for temporary copying of files for the application.  The Read Write access is properly given and everything works but then stops working
    in about 2.5 hours.  The settings are still there, to make things work again typically I add "Everyone" to the security list and apply and then 3 hours later I remove "Everyone" and this refreshes the security setting and things work
    againg for a couple of hours.  Last Cloud server was 2008 R2 and we had no issues.  Recently moved to this new cloud server.  Code has been functioning fine for years and can not migrate it to newer ASP since will have to make quite a few code
    changes.  Obviously a bug which needs to be addressed.  Again the security settings do not disappear but are no longer handled properly every 3 hours or so.

    Hi,
    Is there any other files have the same issue? Please create a test folder and give the same permissions with the directory for ASP 2.0 application to see if the issue still exists.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

    Hello,
    I'm getting an error when trying to add Print Services role in Windows 2012 Standard. I'm getting the same error whether I use the GUI or from PowerShell.
    This is a new server install.
    The PowerShell error follows:
    add-windowsfeature : The request to add or remove features on the specified server failed.
    Installation of one or more roles, role services, or features failed.
    The referenced assembly could not be found. Error: 0x80073701
    At line:1 char:1
    + add-windowsfeature print-services
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature],
        Exception
        + FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWind
       owsFeatureCommand
    Success Restart Needed Exit Code      Feature Result
    False   No             Failed         {}
    Any help with this issue will be greatly appreciated.

    Hi,
    I think you should start with chkdsk C: /F and sfc /scannow.
    Regards.
    Vivian Wang

  • Exchange 2013 management tools installation on windows 2012 standard edition gives error.

    Exchange 2013 management tools installation on windows 2012 standard edition gives following error.
    Does anyone observed this issue ?
    Error:
    The Exchange management tools are supported on servers running Windows Server 2012 and Windows Server 2008 R2 SP1 or later, and also on Windows 8 and Windows 7 client computers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersionForAdminTools.aspx
    My Test lab is having
    Exchange 2013 installed (xyz.local) domain and working fine.
    Now i am installing Exchange Management tools on server which is member of (xyz.local) Domain  (base OS : Windows 2012 standard edition : Windows updated)
    Best Regards
    sameer Prabhune

    Hi Sprabhune,
    It should work.
    Did you install the tool by GUI or cmd?
    Please select "Automatically install Windows Server roles and features that are required to install Exchange Server" to have the Setup wizard install required Windows prerequisites.
    If possible, please try to install the tool on Windows 7/8 client to test.
    Exchange 2013 Prerequisites
    http://technet.microsoft.com/en-us/library/bb691354.aspx
    Frank Wang
    TechNet Community Support

  • Is it possible to install sql server 2008 standard edition in windows server 2008 enterprise edition?

    hi,
    Please help me..
    is it possible to install sql server 2008 standard edition in windows server 2008 enterprise edition?
    will any problem arise?

    Hiya,
    Yes it it possible. No there will not be any problems.
    Short and simple :)

  • Issue of Text Qualiffier after upgrading to SQL Server 2014 Standard

    Hi,
    I'm facing an issue of Text Qualifier after I upgrading my system to SQL Server 2014 Standard Edition (Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
        Feb 20 2014 20:04:26
        Copyright (c) Microsoft Corporation
        Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    I have a csv file with format: Text Qualifier is double pipes ||, Vertical Bar (|) as Column Delimiter and  Row Delimiter is CRLF.
    For example file:
    ||Col1|||||Col2||
    ||ABC|||||XYZ||
    This file is working OK in SQL Server 2008 R2 (SP2) but it does not work in SQL Server 2014. It raised error message while running.
    Error: An error occurred while skipping data rows.
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on MediaAgencyGroup returned error code 0xC0202091.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
    code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error messages posted before this with more information about the failure.
    Any suggestion here?
    Thanks,

    Yes
    There's a difference in the way text qualifiers are parsed from 2012 onwards
    see
    http://www.proactivespeaks.com/2012/06/22/my-5-favorite-sql-2012-ssis-features-so-far/
    http://blog.concentra.co.uk/2013/06/24/ssis-2012-flat-files-now-greatly-improved-but-are-they-good-enough-yet/
    ANyways my preferred way to do this is as below
    http://visakhm.blogspot.in/2014/06/ssis-tips-handling-embedded-text.html
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Issues enabling AlwaysON in SQL Server 2014 Standard

    Hi 
    I am trying to configure AlwaysOn and having issues enabling in SQL Server configuration manager
    OS : Windows Server 2012 R2
    SQL : SQL Server 2014 Standard Edition
    Here is what i see in config manager : 
    The AlwaysOn Availability Groups feature requires the x86(non-Wow) or x64 Enterprise Edition of SQL Server 2012 (or later version) running on Windows Server 2008 (or later version) with WSFC hotfix KB 2494036 installed. This SQL Server edition and/or Windows
    Server system do not meet one or more of these requirements.
    I patched both the nodes and ran the cluster validation as well which didn't report any missing patches. Couldn't find any documentation/solution for this. 
    Can someone please help me with this ???

    Thanks. 
    Is the configuration of Always on FCI is same as Traditional WSFC ?
    Yes just think of it as a regular clustered sql instance
     An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes
    and, possibly, across multiple subnets. 
    https://msdn.microsoft.com/en-us/library/ms189134(v=sql.110).aspx

  • Windows 7 and SQL Server Dependency

    I was told something today which is hard for me to believe.  I was told that Windows 7 installs SQL Server as the default instance, such that if you say install Sql Server 2012 Express, it will always be a secondary instance and never the default instance. 
    I know on the Win 8.1 box i'm typing this on I installed SQL Server 2012 Express as the default instance.  Can someone clarify this for me?
    Thanks

    I was told something today which is hard for me to believe.  I was told that Windows 7 installs SQL Server as the default instance, such that if you say install Sql Server 2012 Express, it will always be a secondary instance and never the default instance. 
    I know on the Win 8.1 box i'm typing this on I installed SQL Server 2012 Express as the default instance.  Can someone clarify this for me?
    Thanks
    Hello,
    When you install SQL server express its instance name will be Machinename\SQLEXPRESS .After this if you want to install default instance you can go ahead and do that.Generally first instance you install becomes default instance unless you specifically give
    name for it.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

    I've been searching for HOURS how to resolve this issue:
    I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
    ======================================================================================
    Rule Check Result
    Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
    This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
    =====================================================================================
    This is the Configuration Report issue:
    Microsoft SQL Server 2014 - System Configuration Check Report
    UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
        KJRTMUpgradeBlockRule     
    Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack.     Failed     The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
    required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
    ====================================================================================
    I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
    out!!!
    Thanks.

    Hi again
    This is the scenario:
    -I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
    -As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
    resolved immediately with the Windows Update service.
    -Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
    Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
    with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
    Now we are on 12.0.2000.8
    Thanks anyway and all of you for your interest!!!

  • SP3 cannot be installed on SQL Server 2008 standard edition 64 bit

    I am getting error during the running of setup of SP3 for SQL Server 2008 Standard edition on windows 2008 R2 enterprise ed.
    Description:
      SQL Server 2008 Setup has encountered an error.
    Problem signature:
      Problem Event Name: SQL100Exception
      Problem Signature 01: SQL2008@RTM@KB2546951
      Problem Signature 02: 0xFE9E43A7
      Problem Signature 03: 0xFE9E43A7
      Problem Signature 04: 0xDC80C325
      Problem Signature 05: 0xDC80C325
      Problem Signature 06: InitializeUIDataAction
      Problem Signature 07: Unknown
      Problem Signature 08: Unknown
      Problem Signature 09: Unknown
      Problem Signature 10: Unknown
      OS Version: 6.1.7601.2.1.0.274.10
      Locale ID: 1033
    Additional information about the problem:
      LCID: 1033
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    Hi,
    I found the log file but I am not able to find any upload file button. It is very big file how can I upload it here?
    Overall summary:
      Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -74274373
      Exit facility code:            914
      Exit error code:               43451
      Exit message:                  The system cannot open the device or file specified. 
      Start time:                    2014-04-10 08:03:59
      End time:                      2014-04-10 08:05:15
      Requested action:              Patch
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140410_080359\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.5500.0%26EvtType%3d0xFE9E43A7%400xDC80C325
    Machine Properties:
      Machine name:                  AD-ITD-SW-SQLDB
      Machine processor count:       16
      OS version:                    Windows Server 2008
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      SWMSSQLSERVER        MSSQL10.SWMSSQLSERVER          Database Engine Services                
    1033                                      10.0.1600.22   
    No       
      Sql Server 2008      SWMSSQLSERVER        MSSQL10.SWMSSQLSERVER          SQL Server Replication                  
    1033                                      10.0.1600.22   
    No       
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Standard Edition    
    10.0.1600.22    No       
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Standard Edition     10.0.1600.22   
    No       
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Standard Edition    
    10.0.1600.22    No       
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Standard Edition     10.0.1600.22    No       
      Sql Server 2008                                                         
    Integration Services                     1033                 Standard Edition    
    10.0.1600.22    No       
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       3
      KBArticle:                     KB2546951
      KBArticleHyperlink:           
      PatchType:                     SP
      AssociatedHotfixBuild:         0
      Platform:                      x64
      PatchLevel:                    10.3.5500.0
      ProductVersion:                10.0.1600.22
      GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0;10.0.4010.0:10.0.4250.0;10.0.5501.0:10.0.5750.0
      PackageName:                   SQLServer2008-KB2546951-x64.exe
      Installation location:         d:\c8811b7ec810308deb\x64\setup\
    User Input Settings:
      ACTION:                        Patch
      ALLINSTANCES:                  False
      CLUSTERPASSIVE:                False
      CONFIGURATIONFILE:            
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTANCENAME:                  <empty>
      QUIET:                         False
      QUIETSIMPLE:                   False
      X86:                           False
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               The rule result report file is not available.
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: System.ComponentModel.Win32Exception
        Message:
            The system cannot open the device or file specified.
        Data:
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetDBProperty(ServiceContainer context, String pathToMsi, String propertyName)
            at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.GetMsiRtmVersion(PackageInstallProperty targetPackage)
            at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.IsApplicablePatch(PatchProperty currentPatch, PackageInstallProperty targetPackage)
            at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.GetInstalledPackages(String instanceName, List`1& installedInstancePackages, List`1& installedSharedPackages, String& returnedErrorMessage)
            at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.CollectProductData()
            at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinitionAllInstances()
            at Microsoft.SqlServer.Configuration.PatchFeatureTree.InitializePatchFeatureTree(ServiceContainer context)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

  • SQL Server 2014 Standard, but only 2 GB RAM used

    Hello,
    I just installed MS SQL Server 2014 Standard Single x64 on a Windows 8 PC. It was bought to replace the Server Express because the RAM limitation of Express.
    I set min server memory to 500 MB and max server memory to 28672 MB. PC has 32 GB Ram.
    Now I start a very crazy procedure/query that is running for hours.
    The problem is now that task manager shows:
    - SQL Server Management Studio (32 Bit): 0% CPU and 135,4 MB RAM
    - SQL Server Windows NT - 64 Bit: 60% CPU and 2.032,6 MB RAM
    If I use: SELECT * FROM sys.dm_os_process_memory  I get:
    physical_memory_in_use_kb : 2124632
    memory_utilization_percentage : 100
    So why is there Management Studio 32 Bit if I installed it through MS SQL Server 2014 Standard Single x64 installation?
    And much more important: Why is only 2 GB RAM used if 32 GB are there and 28 GB should be used?
    kind regards
    Peter

    Hello,
    Could you try to enable Lock Pages in Memory option for the SQL Server service account?
    http://www.sqlcoffee.com/Tuning05.htm
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Create linked server between MS SQL Server 2008 standard edition to MS SQL Server 2008 express edition

    For the captioned issue, is it possible?  We have successfully created linked server between 2 MS SQL server 2008 standard edition, but failed for the standard and express edition.  Is there any trick to setup?  Thanks.

    Hello,
    SQL Server Management Studio Express Edition may not allow to create a linked server, but the workaround is to use the T-SQL. You can use sp_addlinkedserver and sp_addlinkedsrvlogin.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Installing Full-Text Search in SQL Server 2008 Standard

    Hello,
     We have a SQL Server 2008 Standard server, and I need to install full-text search in order to take advantage of some features with Autodesk Vault.  I believe that I understand the procedure to do so, but, does the installation of the setup tools
    and full-text search component cause any interruption to the database instances (or require a reboot)?
    Thanks

    Hi Indiana Grumpycooter,
    Full text search feature is supported by the SQL Server 2008 standard version, so you can install this feature in
    installation page of the SQL Server Installation Wizard. There is an similar example about adding SQL Full-Text Search to an existing SQL Server, you can review the following steps.http://www.techrepublic.com/blog/data-center/adding-sql-full-text-search-to-an-existing-sql-server/
    In addition, you can also install this feature via command line as follows. For more information, see:
    http://msdn.microsoft.com/en-us/library/ms144259(v=sql.100).aspx
    Setup.exe /q /ACTION=Install /FEATURES= Full-Text /INSTANCENAME=MSSQLSERVER /SQLSVCACCOUNT="<DomainName\UserName>" /SQLSVCPASSWORD="<StrongPassword>" /SQLSYSADMINACCOUNTS
    As other post, it will not cause interruption, and you require a reboot after installing Full-Text feature.
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Log File Issue In SQL server 2005 standard Edition

    We have database of size 375GB .The data file has 80 GB free space within .When trying to rebuild the index we had 450 GB free space on the disk where Log file is residing.The rebuild index activity failed due to space issue.added more space and got the
    job done successfully
    The Log file has grow up to 611GB to complete the rebuild index.
    version :SQL server 2005 Standard Edition .Is ther a way to estimate the space required for rebuild index in this version.
    I am aware we notmaly allocate 1.5 times of data file.But in this case It was totaly wrong.
    Any suggestion with examples would be appreciated.
    Raghu

    OK, there's a few things here.
    Can you outline for everybody the recovery model you are using, the frequency with which you take full, differential and transaction log backups.
    Are you selectively rebuilding your indexes or are you rebuilding everything?
    How often are you doing this? Do you need to?
    There are some great resources on automated index maintenance, check out
    this post by Kendra Little.
    Depending on your recovery point objectives I would expect a production database to be in the full recovery mode and as part of this you need to be taking regular log backups otherwise your log file will just continue to grow. By taking a log backup it will
    clear out information from inactive VLF's and therefore allow SQL Server to write back to those VLF's rather than having to grow the log file. This is a simplified version of events, there are caveats.
    A VLF will be marked as active if it still has an open transaction in it or there is a HA option that still requires that data to be available as that data has not been copied to another node yet.
    Most customers that I see take transaction log backups every 15 - 30 minutes, but this really does depend upon how much data your company can afford to lose. That's another discussion for another day.
    Make sure that you take a transaction log backup prior to your job that does your index rebuilds (hopefully a smart job not a sledge hammer job).
    As mentioned previously swapping to bulk logged can help to reduce the size of the amount of information logged during index rebuilds. If you do this make sure to swap back into the full recovery model straight after and perform a full backup. There are
    problems with the ability to do point in time restores whilst in the bulk logged recovery model, so you need to reduce the amount of time you use it.
    Really you also need to look at how your indexes are created does the design of them lead to them being fragmented on a regular basis? Are they being used? Are there better indexes out there that can help performance?
    Hopefully that should put you on the right track.
    If you find this helpful, please mark the post as helpful,
    If you think this solves the problem, please propose or mark it an an answer.
    Please provide details on your SQL Server environment such as version and edition, also DDL statements for tables when posting T-SQL issues
    Richard Douglas
    My Blog: Http://SQL.RichardDouglas.co.uk
    Twitter: @SQLRich

  • Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition?

    Hello,
    Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition? 
    Thanks. 

    Yes, you can replicate from Enterprise edition to Standard edition.  The only caveat is Peer-to-Peer Replication requires all nodes to be Enterprise Edition.
    Brandon Williams (blog |
    linkedin)

Maybe you are looking for