Database Ownership gets messed up with SQL Server 2014 AlwaysON

Hi All,
I am trying to build a nightly refresh process for SQL Server DB from on premise to Azure Cloud (IAAS). The Azure infrastructure is configured as 2 node always on. Every Day a new DB get created with retention period of 7 days. (Another script which deletes
old DB)
Nightly Build Process as Below:
1) DB Backup get copied to Azure Blob Storage 
2) Restore DB on primary Server on Azure
3) Change DB owner to appropriate login on primary Server
4) Backup DB/Log from primary Server and restore it on Secondary Server.
5) Add DB to alwayson temp Group.
6) Failover temp Group and change DB owner to appropriate login. (Application Dependency to have login ID as the owner of the DB).
7) Failback and remove DB from temp group and add it to appropriate group.
During this process somehow the DB ownership gets messed up randomly either on primary or Secondary. 
I can handle the primary server ownership mess-up by adding piece of code to set the ownership in the end, but for secondary I can't change the ownership as the DB is in readonly mode, resulting, when failover happens the application fails to open default DB.
Any lead on the solution would be appreciated.
Thanks,
Viral Shah
Thanks - Viral

Are you using contained databases? If not, is the login on your primary server on Azure the same as the login from your on-premise SQL Server instance as per this
KB article? Keep in mind that SQL Server looks at SID values and not login/password combination. If the login exists on both servers and the database backup is restored, it carries with it
the login SID assigned as the DB owner
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Similar Messages

  • RDS 2012: Compatible with SQL Server 2014 AlwaysOn?

    Is Remote Desktop Services 2012 R2 compatible with SQL Server 2014 AlwaysOn Availability Groups?  Are there any procedural documents available for RDS requirements on how it expects AlwaysOn to be configured?
    Thanks

    Hi,
    Thank you for posting in Windows Server Forum.
    As per my research, we can install SQL server 2014 on RDS Server 2012\R2, you can check below article with step by step guide.
    How to install SQL Server 2014
    In addition for SQL AlwaysOn Consideration there is useful blog (RDS 2012 SQL AlwaysOn Considerations) you can go through for details.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Sharepoint Foundation 2010 compatibility with SQL Server 2014

    Due to a requirement to use Sharepoint without Active Directory access.  I am trying to find explicit confirmation whether Sharepoint Foundation 2010 is compatible with SQL Server 2014.  I have seen that Sharepoint Server 2010 and 2013 are compatible
    with SQL Server 2014 as of CU 1 (released in April).  But there is no mention of Sharepoint Foundation.
    This chart is great except it doesn't mention whether the Foundation versions are supported.
    http://msdn.microsoft.com/en-us/library/gg492257.aspx
    Thanks.

    Note that that is for the Reporting Services component, but not necessarily for the SQL Database Engine component (which comes from the SharePoint Product Group, rather than the SQL Product Group). I haven't seen any confirmation that SharePoint 2010 is
    supported at all with SQL 2014 as a Database Engine.
    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.

  • DB-Library BCP issue with SQL Server 2014

    Hello,
    My application uses DB-Library (ntwdblib.dll) to communicate with SQL Server 2014. We are having issues calling bcp related functions like bcp_init which always returns FAIL status. Our application was working fine with SQL Server 2012 and all other previous
    SQL releases. But we are getting below error in SQL 2014,
    msg 4801, state 1, severity 16 : Insert bulk is not supported over this access protocol.
    Can anyone please help ?
    Thanks,
    Himanshu

    Hi Himanshu_kus,
    Is this still an issue, or can we close the thread?
    [Personal Site] [Blog] [Facebook]

  • SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

    We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.)  Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
    anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
    specifically listed as a SQL DB user tries to use the front end they get an error of:
    Microsoft SQL Server Login
    Connection failed:
    SQL State: '28000'
    SQL Server Error: 18456
    [Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
    After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
    to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
    Thanks a billion in advance ----

    Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
    all other roles, as well as allowing select only, and still have no access for the guest account.
    The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
    and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
    thru MS Access ACCDB, using a (by default) read only OCDB connection.
    This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
    levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
    since the result set would involve hundreds of thousands if not millions of records.
    So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
    as well as running our network on Microsoft's network software.

  • Sql server 2005 reports with sql server 2014

    Can i upload SSRS 2005 reports as it is on SSRS 2014 and use it without doing anything extra or without changing anything ??
    I can use SSRS 2005 reports as it is with SSRS 2012. But for SSRS 2014 not sure.
    h2007

    You can upgrade the the RDL schema will be upgraded.
    Report definition (.rdl) files are automatically upgraded in the following ways:
    When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 or SQL Server 2008 R2 report server in the project properties, the report
    definition is saved in a schema that is compatible with the target server.
    When you upgrade a Reporting Services installation to a SQL Server 2014 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first
    time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
    Reports are not upgraded when you upload a report definition file directly to the report server or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying
    problems in the report are detected. For more information, see Reporting Services Backward Compatibility.
    For more information about new features for SQL Server 2014 Reporting Services (SSRS), see
    What's New (Reporting Services).
    Check the below Microsoft link for more information
    http://msdn.microsoft.com/en-us/library/ms143674.aspx
    Mudassar

  • Error in VS2010 when connecting with SQL Server 2014

    I have SQL2014 Express installed locally but it is not detected by VS2010. Why would I need to have the 2008 version?

    http://blogs.msdn.com/b/webdev/archive/2010/05/03/visual-studio-2010-support-with-sql-server.aspx
    It proably only goes to SQL 2008. I don't recall pointing VS2010 to SQL Server 2012 either.
    Maybe, you should post to the below fourm.
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=visualstudio

  • Is SSRS 2012 compatible with SQL Server 2014?

    Will it still work if a DW database is in SQL Server 2014 but the reporting services is in SSRS 2012?

    Very likely. If not, probably will be at the next service pack.
    Kalman Toth Database & OLAP Architect
    T-SQL Scripts at sqlusa.com
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • Sql server 2014 AlwaysON issue

    Hi:
    I am configuring AlwaysON availability groups with one primary and one replica, on 2014 server
    things I am done with:
    - both the systems are in windows cluster
    - Cluster service is on on both the servers
    - Enabled AlwaysOn from COnfiguration Manager.
    - Hadr_endpoint on port 5022 is STARTED.
    In the Listener Tab, I am choosing the option 'Create an Availablity Group' and I am using the DHCP network mode, port 1433.
    I am not using static IP
    I get the following error:
    Failed to join the database 'DB1' to the availability group 'AG01' on the availability replica 'Server2'. (Microsoft.SqlServer.Smo)
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
    The connection to the primary replica is not active.  The command cannot be processed. (Microsoft SQL Server, Error: 35250)

    can you try to see,is that works?
    http://mssqlwiki.com/2013/06/20/the-connection-to-the-primary-replica-is-not-active-the-command-cannot-be-processed/
    http://blogs.msdn.com/b/alwaysonpro/archive/2013/12/09/trouble-shoot-error.aspx
    http://sqlserver-help.com/tag/the-connection-to-the-primary-replica-is-not-active-the-command-cannot-be-processed/
    Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.

  • Database Mail not working with SQL Server Agent

    I'm running SQL Server 2005 Standard edition 64 bit with SP2 on a 64 bit machine. 
    Database mail does not work with SQL Server Agent.  When I configure SQL Server Agent to use database mail the test email button is greyed out and inactive therefore I cannot send emails using operators or for jub success failure etc. 
    I've read that there was supposed to be a fix for this with SP1 but I have SP2 and still receive the same problem.  Please can somebody help as I do not wish to use SQL Mail as a work around due to this becomming redundant in future versions of SQL Server.
    Kind Regards

    The problems solved
    steps:
    1)we create a mail profile at at Managment->Database Mail ,of SQL Managment
    2)we set this account as "default" at Managment->Database Mail -> Configure Database Mail -> Manage profile security
    3)At tab "Alert System" of SQL Server Agent properties , we check the "Enable mail profile" , Mail System=Database Mail, Mail profile = "the profile we already create"
    4)we create a new operator at "Operators" of sql agent, where at "notification options" -> "Email name" we put the mail where we want to sent the agent the mails at failured job
    5)We go at a specific job, at tab "Notifications" ,we check the "email" check box and then we choose the operator we just create, at the text box next to check box.
    I hope not to forget something
    Thank You all for the help

  • Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

    I tried to install ,deleted and re-installed several times and no help at all.
    visual studio 2013 with update 2 rc and adk installed in my computer.
    error code: 0x851a0019
    error messege in setup: could not find the database engine startup handle
    edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
    logs:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 13:53:29
      End time:                      2014-04-03 14:47:48
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  ARIELUBA-PC
      Machine processor count:       8
      OS version:                    Windows 8
      OS service pack:               
      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  Configured
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             Database Engine Services                 1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             SQL Server Replication                   1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    Database Engine Services            
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    SQL Server Replication              
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3412.0     No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
      Installation edition:          Evaluation
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Hebrew_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            ARIELUBA-PC\Arie Luba
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   
      CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
      CLTSTARTUPTYPE:                Manual
      CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               Manual
      CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     ARIELUBA-PC\Arie Luba
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Hebrew_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           ARIELUBA-PC\Arie Luba
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Master Data Services
      Status:                        Passed
      Feature:                       Distributed Replay Client
      Status:                        Passed
      Feature:                       Distributed Replay Controller
      Status:                        Passed
      Feature:                       Integration Services
      Status:                        Passed
      Feature:                       Data Quality Client
      Status:                        Passed
      Feature:                       Analysis Services
      Status:                        Passed
      Feature:                       Reporting Services - SharePoint
      Status:                        Passed
      Feature:                       Reporting Services Add-in for SharePoint Products
      Status:                        Passed
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
    2014-04-03 14:14:28.01 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    2014-04-03 14:14:28.01 Server      UTC adjustment: 3:00
    2014-04-03 14:14:28.01 Server      (c) Microsoft Corporation.
    2014-04-03 14:14:28.01 Server      All rights reserved.
    2014-04-03 14:14:28.01 Server      Server process ID is 7148.
    2014-04-03 14:14:28.01 Server      System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
    2014-04-03 14:14:28.01 Server      Authentication mode is WINDOWS-ONLY.
    2014-04-03 14:14:28.01 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-04-03 14:14:28.01 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2014-04-03 14:14:28.01 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-04-03 14:14:28.01 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "Hebrew_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2014-04-03 14:14:28.28 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2014-04-03 14:14:28.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-03 14:14:28.28 Server      Detected 8099 MB of RAM. This is an informational message; no user action is required.
    2014-04-03 14:14:28.28 Server      Using conventional memory in the memory manager.
    2014-04-03 14:14:28.31 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2014-04-03 14:14:28.34 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-03 14:14:28.36 Server      Query Store settings initialized with enabled = 1, 
    2014-04-03 14:14:28.36 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-03 14:14:28.36 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-04-03 14:14:28.38 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-04-03 14:14:28.39 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-03 14:14:28.39 spid8s      Warning ******************
    2014-04-03 14:14:28.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-03 14:14:28.40 spid8s      Starting up database 'master'.
    2014-04-03 14:14:28.42 Server      Software Usage Metrics is disabled.
    2014-04-03 14:14:28.48 Server      CLR version v4.0.30319 loaded.
    2014-04-03 14:14:28.56 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-03 14:14:28.62 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.63 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.64 spid8s      SQL Trace ID 1 was started by login "sa".
    2014-04-03 14:14:28.64 spid8s      Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
    2014-04-03 14:14:28.65 spid16s     Password policy update was successful.
    2014-04-03 14:14:28.66 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-04-03 14:14:28.66 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-03 14:14:28.66 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-04-03 14:14:28.67 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-03 14:14:28.67 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    ________________________________________________________________________________________________

    Is it okay? (see below)
    ;SQL Server 2014 Configuration File
    [OPTIONS]
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 
    ACTION="Install"
    ; Detailed help for command line argument ROLE has not been defined yet. 
    ROLE="AllFeatures_WithDefaults"
    ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 
    ENU="True"
    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 
    UIMODE="Normal"
    ; Setup will not display any user interface. 
    QUIET="False"
    ; Setup will display progress only, without any user interaction. 
    QUIETSIMPLE="False"
    ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 
    UpdateEnabled="True"
    ; 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"
    ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 
    USEMICROSOFTUPDATE="False"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
    will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 
    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
    ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
    or a Windows Update service through the Window Server Update Services. 
    UpdateSource="MU"
    ; Displays the command line parameters usage 
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console. 
    INDICATEPROGRESS="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 the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 
    INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 
    INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
    ; 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"
    ; 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 the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 
    INSTANCEID="MSSQLSERVER"
    ; The computer name that the client communicates with for the Distributed Replay Controller service. 
    CLTCTLRNAME="SQLDRC"
    ; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 
    CTLRUSERS="ARIELUBA-PC\Arie Luba"
    ; The account used by the Distributed Replay Controller service. 
    CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
    ; The startup type for the Distributed Replay Controller service. 
    CTLRSTARTUPTYPE="Manual"
    ; The account used by the Distributed Replay Client service. 
    CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
    ; The startup type for the Distributed Replay Client service. 
    CLTSTARTUPTYPE="Manual"
    ; The result directory for the Distributed Replay Client service. 
    CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
    ; The working directory for the Distributed Replay Client service. 
    CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
    ; RSInputSettings_RSInstallMode_Description 
    RSINSTALLMODE="DefaultNativeMode"
    ; RSInputSettings_RSInstallMode_Description 
    RSSHPINSTALLMODE="SharePointFilesOnlyMode"
    ; Specify the installation directory. 
    INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
    ; Agent account name 
    AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
    ; Auto-start service after installation.  
    AGTSVCSTARTUPTYPE="Manual"
    ; Startup type for Integration Services. 
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account. 
    ISSVCACCOUNT="NT Service\MsDtsServer120"
    ; The name of the account that the Analysis Services service runs under. 
    ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
    ; Controls the service startup type setting after the service has been created. 
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services. 
    ASCOLLATION="Hebrew_CI_AS"
    ; The location for the Analysis Services data files. 
    ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files. 
    ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files. 
    ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files. 
    ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files. 
    ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.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="ARIELUBA-PC\Arie Luba"
    ; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 
    ASSERVERMODE="MULTIDIMENSIONAL"
    ; CM brick TCP communication port 
    COMMFABRICPORT="0"
    ; How matrix will use private networks 
    COMMFABRICNETWORKLEVEL="0"
    ; How inter brick communication will be protected 
    COMMFABRICENCRYPTION="0"
    ; TCP port used by the CM brick 
    MATRIXCMBRICKCOMMPORT="0"
    ; 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="Hebrew_CI_AS"
    ; Account for SQL Server service: Domain\User or system account. 
    SQLSVCACCOUNT="NT Service\MSSQLSERVER"
    ; Windows account(s) to provision as SQL Server system administrators. 
    SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express. 
    ADDCURRENTUSERASSQLADMIN="True"
    ; 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="Automatic"
    ; 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 Service\ReportServer"
    ; 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"
    ; Add description of input argument FTSVCACCOUNT 
    FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

  • MS SQL Server 2014: Error inserting into Temp table with index and identity field

    In this thread, I mentioned a problem with SQL Server 2014:
    SQL Server 2014: Bug with IDENTITY INSERT ON
    The question was answered, it is a bug. To keep you informed on this issue, I open this discussion.
    Problem:
    The code below works perfectly fine on MS SQL Server 2008 R2 and MS SQL Server 2012, but gives an error every second time the proc is executed on MS SQL Server 2014. If I do not define any index on the temp table, the problem disappears. Defining the index
    after the insert, does not help.
    SET NOCOUNT ON
    GO
    IF EXISTS (SELECT 1 FROM sys.procedures WHERE name = 'usp_Test') DROP PROC dbo.usp_Test;
    GO
    CREATE PROC dbo.usp_Test AS
    BEGIN
    SET NOCOUNT ON
    CREATE TABLE #Source(ID integer NOT NULL);
    INSERT INTO #Source VALUES (1), (2), (3);
    CREATE TABLE #Dest (ID integer IDENTITY(1,1) NOT NULL);
    CREATE INDEX #IDX_Dest ON #Dest (ID);
    PRINT 'Check if the insert might cause an identity crisis';
    SELECT 'Source' AS SourceTable, * FROM #Source;
    SELECT 'Destination' AS DestTable, * FROM #Dest;
    SET IDENTITY_INSERT #Dest ON;
    PRINT 'Do the insert';
    INSERT INTO #Dest (ID) SELECT ID FROM #Source;
    PRINT 'Insert ready';
    SET IDENTITY_INSERT #Dest OFF;
    SELECT * FROM #Dest;
    DROP TABLE #Source;
    DROP TABLE #Dest;
    END;
    GO
    PRINT 'First execution of the proc, everything OK';
    EXEC dbo.usp_Test;
    PRINT '';
    PRINT 'Second execution of the proc, the insert fails.';
    PRINT 'Removing the index #IDX_Dest causes the error to disappear.';
    EXEC dbo.usp_Test;
    GO
    DROP PROC dbo.usp_Test;
    GO

    There is some progress. Communication from a former Microsoft employee tells us this:
    Shivendra Vishal
    Engineer at Microsoft
    I am no longer with MS, and I do not have code access, however from the public symbols, I could make out following:
    sqlmin!SetidentI2I4+0x1f3:
    000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] ds:00000000`00000000=????????????????
    ExceptionAddress: 000007fef4d865d3 (sqlmin!SetidentI2I4+0x00000000000001f3)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000000
    Attempt to read from address 0000000000000000
    This is a read AV and from registers it is clear that we were trying to move the value of location pointed by qword of register rax which is not valid:
    rax=0000000000000000 rbx=0000000000000038 rcx=0000000000001030
    rdx=0000000000000006 rsi=00000001f55def98 rdi=00000000106fd070
    rip=000007fef4d865d3 rsp=00000000106fcf40 rbp=00000000106fcfe9
    r8=0000000000000000 r9=00000001f55def60 r10=00000001f55defa0
    r11=00000000106fcd20 r12=0000000000000000 r13=0000000000000002
    r14=00000001f49c3860 r15=00000001f58c0040
    iopl=0 nv up ei pl nz na po nc
    cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
    The stack is:
    # Child-SP RetAddr Call Site
    00 00000000`106fcf40 000007fe`f30c1437 sqlmin!SetidentI2I4+0x1f3
    01 00000000`106fd050 000007fe`f474e7ce sqlTsEs!CEsExec::GeneralEval4+0xe7
    02 00000000`106fd120 000007fe`f470e6ef sqlmin!CQScanUpdateNew::GetRow+0x43d
    03 00000000`106fd1d0 000007fe`f08ff517 sqlmin!CQueryScan::GetRow+0x81
    04 00000000`106fd200 000007fe`f091cebe sqllang!CXStmtQuery::ErsqExecuteQuery+0x36d
    05 00000000`106fd390 000007fe`f091ccb9 sqllang!CXStmtDML::XretDMLExecute+0x2ee
    06 00000000`106fd480 000007fe`f08fa058 sqllang!CXStmtDML::XretExecute+0xad
    07 00000000`106fd4b0 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
    08 00000000`106fd5f0 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
    09 00000000`106fd7e0 000007fe`f152cfaa sqllang!CSQLSource::Execute+0x86c
    0a 00000000`106fd9b0 000007fe`f152c9e8 sqllang!CStmtExecProc::XretLocalExec+0x25a
    0b 00000000`106fda30 000007fe`f152a1d8 sqllang!CStmtExecProc::XretExecExecute+0x4e8
    0c 00000000`106fe1e0 000007fe`f08fa058 sqllang!CXStmtExecProc::XretExecute+0x38
    0d 00000000`106fe220 000007fe`f08fb66b sqllang!CMsqlExecContext::ExecuteStmts<1,1>+0x427
    0e 00000000`106fe360 000007fe`f08fac2e sqllang!CMsqlExecContext::FExecute+0xa33
    0f 00000000`106fe550 000007fe`f0902267 sqllang!CSQLSource::Execute+0x86c
    10 00000000`106fe720 000007fe`f0909087 sqllang!process_request+0xa57
    11 00000000`106feee0 000007fe`f2bf49d0 sqllang!process_commands+0x4a3
    12 00000000`106ff200 000007fe`f2bf47b4 sqldk!SOS_Task::Param::Execute+0x21e
    13 00000000`106ff800 000007fe`f2bf45b6 sqldk!SOS_Scheduler::RunTask+0xa8
    14 00000000`106ff870 000007fe`f2c136ff sqldk!SOS_Scheduler::ProcessTasks+0x279
    15 00000000`106ff8f0 000007fe`f2c138f0 sqldk!SchedulerManager::WorkerEntryPoint+0x24c
    16 00000000`106ff990 000007fe`f2c13246 sqldk!SystemThread::RunWorker+0x8f
    17 00000000`106ff9c0 000007fe`f2c13558 sqldk!SystemThreadDispatcher::ProcessWorker+0x3ab
    18 00000000`106ffa70 00000000`775d59ed sqldk!SchedulerManager::ThreadEntryPoint+0x226
    19 00000000`106ffb10 00000000`7780c541 kernel32!BaseThreadInitThunk+0xd
    1a 00000000`106ffb40 00000000`00000000 ntdll!RtlUserThreadStart+0x21
    Unassembling the function:
    000007fe`f4d8658e 4c8b10 mov r10,qword ptr [rax]
    000007fe`f4d86591 4533e4 xor r12d,r12d
    000007fe`f4d86594 410fb7d5 movzx edx,r13w
    000007fe`f4d86598 4533c9 xor r9d,r9d
    000007fe`f4d8659b 4533c0 xor r8d,r8d
    000007fe`f4d8659e 488bc8 mov rcx,rax
    000007fe`f4d865a1 4489642420 mov dword ptr [rsp+20h],r12d
    000007fe`f4d865a6 41ff5230 call qword ptr [r10+30h]
    000007fe`f4d865aa 8b5597 mov edx,dword ptr [rbp-69h]
    000007fe`f4d865ad 4c8b10 mov r10,qword ptr [rax]
    000007fe`f4d865b0 4489642438 mov dword ptr [rsp+38h],r12d
    000007fe`f4d865b5 4489642430 mov dword ptr [rsp+30h],r12d
    000007fe`f4d865ba 458d442401 lea r8d,[r12+1]
    000007fe`f4d865bf 4533c9 xor r9d,r9d
    000007fe`f4d865c2 488bc8 mov rcx,rax
    000007fe`f4d865c5 c644242801 mov byte ptr [rsp+28h],1
    000007fe`f4d865ca 4488642420 mov byte ptr [rsp+20h],r12b
    000007fe`f4d865cf 41ff5250 call qword ptr [r10+50h]
    000007fe`f4d865d3 488b10 mov rdx,qword ptr [rax] <=================== AV happened over here
    000007fe`f4d865d6 488bc8 mov rcx,rax
    000007fe`f4d865d9 4c8bf0 mov r14,rax
    000007fe`f4d865dc ff5268 call qword ptr [rdx+68h]
    000007fe`f4d865df 488d55e7 lea rdx,[rbp-19h]
    000007fe`f4d865e3 4c8b00 mov r8,qword ptr [rax]
    000007fe`f4d865e6 488bc8 mov rcx,rax
    000007fe`f4d865e9 41ff5010 call qword ptr [r8+10h]
    000007fe`f4d865ed f6450a04 test byte ptr [rbp+0Ah],4
    I remember few issues with scan2ident function, I am not sure if they have fixed it however it appears that this is intoduced to SQL 2014 and we need help from MS to get this resolved as it needs code analysis.
    It is not getting simulated for other versions of SQL apart from SQL 2014.
    Also to add, interestingly, the value of rax is not visibly changed and it was successfully passed on to rcx, which has a valid value, so something should have changed the value of rax inside call to function using call qword ptr [r10+50h], and looking at this
    it appears that it might be a list of functions and we are going at particular offset [50h]. So, bottom line is that the call to function qword ptr [r10+50h], should be changing something in rax, and debugging/analyzing this code might give us some more idea.

  • SQL SERVER 2014 SSMS

    All right, I'm at wits end. After three weeks of downloading, installing, uninstalling, downloading … ad nauseam; SQL SERVER 2014 (SQLEXPRADV_64_ENU.exe) in an attempt to obtain Sql  Server Management
    Studio (SSMS). I’m working on a Lenovo Thinkpad with Windows 7 Professional. SQL Server 2014 is working fine. However, no where can I find the SSMS executable. I do find the SSMS icon file (ssms.ico), ssms.pkgdef,  ssms.pkgundef, ssms.splash.bmp, ssms.winprf
    all in C:/Program Files (x86)/Microsoft SQL Server/120/Tools/Binn/MangementStudio; but no ssms.exe.  In desperation I did reload SQL SERVER 2008 in order to have SSMS 2008 and it is up and running but doesn’t open the SQL SERVER 2014 database engine (therefore
    I have no access to my database with the 2008 tool).  How can I get SSMS 2014 up and running? I really hate to have to uninstall the current instance, re-download and install a new instance and then again find the SSMS executable isn’t there (that process
    takes a full day). Any suggestions would be greatly appreciated.

    All right. to wrap things up I finally gave up, uninstalled all the programs associated with SQL Server 2014 (about a one hour job), then again downloaded SQL Server 2014. After reading all I could about the various versions
    of the SQL Server downloads, I selected SQLEXPRWT_x64_ENU version instead of the advanced version that a tutorial suggested the first time I attempted to download the software. The SQLEXORWT is suppose to contain ssms. Once downloaded I went through the
    install process (another 3 hours) and low and behold there was the ssms executable.
    I was able to get everything up and running, able to connect my databases to ssms and able to get access to my database on Visual Studio 2012 through command line code. I decided to use the localDB database. The biggest problem
    I had in writing the connection string was that most of the instructions on the net indicated the Server name to be (localdb)\v11.0. This didn't work for me and after some searching and using the command line found the Server name on my machine was actually
    (localdb)\MSSQLLocalDB.
    I still have one irritating problem. Although I can connect SSMS to my databases, and although I can connect to the databases in Visual Studio through code, I cannot connect Visual Studio itself to the database. I can connect
    Visual Studio to the Server but not to the databases. When I attempt to connect to the database I get numerous error messages the two most prominentbeing "permission denied" and "Could not load file or assembly 'Microsoft.Sdk.Stc, Version=11.0.0.0,
    Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies" . Any thoughts on why Visual Studio 2012 won't connect to the databases would be greatly appreciated.
                T

  • SQL server 2014 DB creation issue

    Hi,
    I have created VM (windows server 2012) which is installed with SQL server 2014 standard version from gallery. when I tried to create a DB in SQL server it is taking too much time (more than half an hour it will be in the executing state) to create. so I
    restarted SQL server and finally deleted the VM and created new one but no luck, the problem remains the same.
    please help me to resolve this.
    thanks in advance!!
    regards,
    Naveen

    Naveen you need to show us the query you ran to create Database. If you scripted out Database script from some other huge database it would have huge initial size and it would take time for SQL Server to get thoes space plus instant file initialization
    also comes into picture. If that is missing it would again take too much time
    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

  • Installing App-Controller DB on SQL Server 2014

    Hi Folks,
    I have SCVMM 2012 installed on a Windows Server 2012 R2 server with SQL Server 2014. I would like to install the App-Controller s/w, however I am getting an error at the configure SQL server database stage "The specified SQL Server instance is not a
    supported version or edition"
    Does anyone know a work-a-round for this?

    Hi AndyW
    Which edition of SQL Server are you using? (e.g. Express, Developer, Standard, Datacenter)
    App Controller won't install on Express or Developer.
    Regards
    Richard
    This posting is provided "AS IS" with no warranties, and confers no rights.

Maybe you are looking for