SQL Server 2014 New T-SQL Features

I have seen the following new T-SQL features:
1. In-memory OLTP tables.
2. Inline specification of CLUSTERED and NONCLUSTERED indexes is now allowed for disk-based tables.
3. The SELECT … INTO statement is improved and can now operate in parallel.
Any others? Thanks.
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

http://windowsitpro.com/sql-server-2014/top-ten-new-features-sql-server-2014
http://www.sqlpass.org/sqlserver2014/Webinars.aspx
Enhanced query processing for better performance without app changes.
Buffer Pool extension to SSDs for faster paging.
Resource Governor controls IO along with CPU and memory.
Enhanced Always On now supports 8 secondary for better HA (High Availability

Similar Messages

SQL Server 2014 New Database Design Features

SQL Server 2014 has three major database design related features:
1. In-memory OLTP tables (Hekaton)
2. Inline INDEX declaration in CREATE TABLE
3. Updateable clustered columnstore index
Any other new feature? Thanks.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Design & Programming
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

http://windowsitpro.com/sql-server-2014/top-ten-new-features-sql-server-2014
http://www.sqlpass.org/sqlserver2014/Webinars.aspx
Enhanced query processing for better performance without app changes.
Buffer Pool extension to SSDs for faster paging.
Resource Governor controls IO along with CPU and memory.
Enhanced Always On now supports 8 secondary for better HA (High Availability

SQL server 2014 express with advanced features

Dear All,
i am migrating from SQL server 2008 r2 enterprize edition to 2014 express with advanced service..
Please, guide me what will be consideration points ..
Regarding Reporting Services ..
also TSQL support ..
Help must appreciated ..
Dilip Patil..

i am migrating from SQL server 2008 r2 enterprize edition to 2014 express with advanced service..
Please, guide me what will be consideration points ..
Regarding Reporting Services ..
also TSQL support ..
Inplace upgrade of SQL server 2008 r2 enterprise to SQL server 2014 express is not supported. But you can do side by side which I would not recommend. Please see
Version and edition upgrade supported
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

Why can't I log into my "Local" sql server (sql server 2014) with my Sql Server Authentication UID ?

I just got a new work station (win7 Pro) which has the following sql server
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
returns
12.0.2254.0 RTM Developer Edition (64-bit)
Select @@version
returns
Microsoft SQL Server 2014 - 12.0.2254.0 (X64)
Jul 25 2014 18:52:51
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
I added/created a new (random) user account to this server [joe123] and made him sa and mapped him to everything, the password never expires, ...
when I try to login to this local server the login fails, but I can log into this server with my windows integrated account (also sa). What do I need to do so that the joe123 account can login to the server
Rich P

Check if both "SQL Server and Windows Authentication mode" is set (not just Windows Authentication mode). Server-->right click and select properties --> Security
Satish Kartan http://www.sqlfood.com/

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 2014 set password for backup file

We are using sql server 2014, all our databases will be automatically backed up as per schedule. Now need to protect our
backed up databases with password. We have tried below queries:
BACKUP DATABASE teknomectest TO DISK='C:\test.BAK' WITH MEDIAPASSWORD='sqlpas'
Executing it shows below error
One or more of the options (mediapassword) are not supported for this statement.
Analyzing which we came to know this feature is blocked in sql server 2012 itself. Is there any other way to protect bak file.
Bala
Bala

MayurPaghal, Bala said he is using SQL server 2014
Beginning with SQL Server 2012, the PASSWORD and MEDIAPASSWORD options
are discontinued for creating backups. It is still possible to restore backups created with passwords.
https://msdn.microsoft.com/en-us/library/ms186865.aspx

Unable to connect to report server - on Win 8.1 and SQL Server 2014

unable to connect to report server on Win 8.1 and SQL Server 2014 version
Microsoft SQL Server 2014 - 12.0.2000.8 (Intel X86)
   Feb 20 2014 19:20:46
   Copyright (c) Microsoft Corporation
   Express Edition on Windows NT 6.3 <X64> (Build 9600: ) (WOW64)
Thanks

Hi,
I suggest you check out the following article for the steps of installing
Database Engine Services and SQL Server Reporting Service.
http://msdn.microsoft.com/en-us/library/ms143711.aspx
Best Regards,
Tracy
Tracy Cai
TechNet Community Support

Want to know what is improvement in FILEstram storage feature from SQL SERVER 2008 to SQL SERVER 2014

Hi All ,
want to know what is improvement in FILEstram storage feature from SQL SERVER 2008 to SQL SERVER 2014
Regards,
Manish

Hello Manish,
See
What's New in SQL Server 2012
What's New in SQL Server 2014
Nothing really new around that feature.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Trouble Turneing on FileStream/Ad Hoc Query with new SQL Server 2014 64-BIt Version

SQL Server Help,
I have recently installed SQL SERVER 2014 on my Window 7 SP1 Acer laptop.
I am trying to do a simple upload of an Excel file into SQL Server using the OPENROWSET command:
Which I found requires some configuration change I attempted below.
When I execute this:
execute sp_configure 'show advanced options', 1;
RECONFIGURE;
execute sp_configure 'Ad Hoc Distributed Queries', 1;
RECONFIGURE;
GO
I get this message
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5593, Level 16, State 1, Line 2
FILESTREAM feature is not supported on WoW64. The feature is disabled.
Msg 15123, Level 16, State 1, Procedure sp_configure, Line 62
The configuration option 'Ad Hoc Distributed Queries' does not exist, or it may be an advanced option.
Msg 5593, Level 16, State 1, Line 4
FILESTREAM feature is not supported on WoW64. The feature is disabled.
When I go to the SQL Server Services and Properties on the Server and try to change the FileStream options to be on..I get the error:
"There was an unknown error applying the FILESTREAM settings. Check the parameters are valid (0x80070002)."
Perhaps my issue is with the Windows Share Name: . I have put in a local driver C:\A_Excel....also the computer name, my user ID. Is there a special format or way to define a Share Name that I am unaware of?
Is there a way to fix this? Can I not load Excel files with a 64-Bit system? Or what is the easiest way that I can do this with my configuration?
Thanks for any help.

FILESTREAM feature is not supported on WoW64. The feature is disabled.
By the error message it seems you have a 64 bit OS, but have installed a 32 bit SQL Server and here in WoW64 mode filestream seems to be not supported. Install a 64 bit SQL Server instead.
Olaf Helper
[ Blog] [ Xing] [ MVP]

New SQL Server 2014 permissions chart is available

I have created a new permissions poster for the SQL Server 2014 Database Engine. It includes the 3 permissions that are new in SQL Server 2014. It is available at
http://go.microsoft.com/fwlink/?LinkId=229142
Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

Thanks Rick.
Regards, Vishal Srivastava

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

Overlapped I/O error 997 installing SQL Server 2014 Express on Windows Server 2012 R2

I'm attempting to install SQL Server 2014 Express on a Windows Server 2012 R2 system. When I do the install, it fails (several times) with an "Error: 997. Overlapped I/O operation is in progress.". From searching the web, I can see many people
have had this problem with this installer and other non-SQL server installers.
I've tried every solution I can find discussed, but none help with my problems The system is fully updated, with the exception of the KB2538243 (VC 2008 SP1 redist), which is probably failing for the same reason.
I've tried removing several updates mentioned in other articles (KB2918614). I've confirmed that I'm not using a temporary profile.
Does anyone have an idea of how I can solve this issue?
Thanks,
Zack
Partial detail from install log file:
Detailed results:
Feature: Management Tools - Complete
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, and then try the setup process again.
Component name: Microsoft Visual Studio 2010 Redistributables
Component error code: 997
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
Error description: Error 997.Overlapped I/O operation is in progress.
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=vc_red.msi%40ProcessComponents%40997
Feature: Client Tools Connectivity
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, and then try the setup process again.
Component name: Microsoft Visual Studio 2010 Redistributables
Component error code: 997
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
Error description: Error 997.Overlapped I/O operation is in progress.
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=vc_red.msi%40ProcessComponents%40997
Partial detail from component log file:
MSI (s) (D8:3C) [15:18:29:173]: Resolving source.
MSI (s) (D8:3C) [15:18:29:173]: Resolving source to launched-from source.
MSI (s) (D8:3C) [15:18:29:173]: Setting launched-from source as last-used.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{1D8E6291-B0D5-35EC-8441-6616F567A0F7}'.
MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR ==> C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\
MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR product ==> {1D8E6291-B0D5-35EC-8441-6616F567A0F7}
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: A general error running CryptAcquireContext
MSI (s) (D8:3C) [15:18:29:188]: Determining source type
MSI (s) (D8:3C) [15:18:29:188]: Source type from package 'VC_RED.MSI': 2
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: SourceHash database file already exists. Deleting it.
MSI (s) (D8:3C) [15:18:29:204]: Note: 1: 2262 2: SourceHash 3: -2147287038
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: New Hash Database creation complete.
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:997
MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: Failed to CreateContentHash of the file: install.res.1040.dll: for computing its hash. Error: 997
MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Failed to create hash for the install source files
MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: SecureRepair Failed. Error code: 3e561F257D8
Action start 15:18:29: ProcessComponents.
MSI (s) (D8:3C) [15:19:28:843]:
Error 997.Overlapped I/O operation is in progress.

Alberto,
Thanks for your help. Unfortunately, I've already tried that. I did try it again and I get an "This update is not applicable to your computer."
I tried to post the Windows Update log, but it was too large. I've posted some of it below.
Here is the WU log:
2015-02-06 11:24:25:793
5048 50
Misc =========== Logging initialized (build: 7.9.9600.17489, tz: -0500) ===========
2015-02-06 11:24:25:793
5048 50
Misc = Process: C:\Windows\system32\wusa.exe
2015-02-06 11:24:25:793
5048 50
Misc = Module: C:\Windows\System32\wuapi.dll
2015-02-06 11:24:25:793
5048 50
COMAPI ----------- COMAPI: IUpdateServiceManager::AddScanPackageService -----------
2015-02-06 11:24:25:793
5048 50
COMAPI - ServiceName = Windows Update Standalone Installer
2015-02-06 11:24:25:793
5048 50
COMAPI - ScanFileLocation = C:\c5f288db3c43a7e4613232ca1a3c\wsusscan.cab
2015-02-06 11:24:25:808
920 111c
Misc =========== Logging initialized (build: 7.9.9600.17489, tz: -0500) ===========
2015-02-06 11:24:25:808
920 111c
Misc = Process: C:\Windows\system32\svchost.exe
2015-02-06 11:24:25:808
920 111c
Misc = Module: c:\windows\system32\wuaueng.dll
2015-02-06 11:24:25:808
920 111c
Service *************
2015-02-06 11:24:25:808
920 111c
Service ** START ** Service: Service startup
2015-02-06 11:24:25:808
920 111c
Service *********
2015-02-06 11:24:25:824
920 111c
IdleTmr Non-AoAc machine. Aoac operations will be ignored.
2015-02-06 11:24:25:824
920 111c
Agent * WU client version 7.9.9600.17489
2015-02-06 11:24:25:824
920 111c
Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2015-02-06 11:24:25:824
920 111c
Agent * Base directory: C:\Windows\SoftwareDistribution
2015-02-06 11:24:25:824
920 111c
Agent * Access type: No proxy
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
2015-02-06 11:24:25:824
920 111c
Agent * Network state: Connected
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
2015-02-06 11:24:25:824
920 111c
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
2015-02-06 11:24:25:855
920 b64
Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
2015-02-06 11:24:25:855
920 111c
Agent *********** Agent: Initializing global settings cache ***********
2015-02-06 11:24:25:887
920 111c
Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2015-02-06 11:24:25:887
920 111c
Agent * WSUS server: <NULL>
2015-02-06 11:24:25:887
920 111c
Agent * WSUS status server: <NULL>
2015-02-06 11:24:25:887
920 111c
Agent * Target group: (Unassigned Computers)
2015-02-06 11:24:25:887
920 111c
Agent * Windows Update access disabled: No
2015-02-06 11:24:25:902
920 b64
WuTask WuTaskManager delay initialize completed successfully..
2015-02-06 11:24:25:902
920 b64
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
AU Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2015-02-06 19:30:54, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
AU Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2015-02-06 19:30:54, not idle-only, not network-only
2015-02-06 11:24:25:902
920 b64
Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2015-02-06 11:24:25:902
920 b64
Report CWERReporter::Init succeeded
2015-02-06 11:24:25:902
920 b64
Agent *********** Agent: Initializing Windows Update Agent ***********
2015-02-06 11:24:25:902
920 b64
DnldMgr Download manager restoring 0 downloads
2015-02-06 11:24:25:902
920 111c
AU ########### AU: Initializing Automatic Updates ###########
2015-02-06 11:24:25:902
920 111c
AU AIR Mode is disabled
2015-02-06 11:24:25:902
920 111c
AU # Approval type: Scheduled (User preference)
2015-02-06 11:24:25:902
920 111c
AU # Auto-install minor updates: Yes (User preference)
2015-02-06 11:24:25:902
920 111c
AU # Will interact with non-admins (Non-admins are elevated (User preference))
2015-02-06 11:24:25:902
920 111c
Misc WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=2250
2015-02-06 11:24:25:918
920 111c
AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
2015-02-06 11:24:25:918
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:918
920 111c
AU AU finished delayed initialization
2015-02-06 11:24:25:933
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:933
920 111c
AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
2015-02-06 11:24:25:933
920 b64
Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\a487aa0f-3e53-4fee-a784-6171b00254e4\Source.cab with dwProvFlags 0x00000080:
2015-02-06 11:24:25:933
920 111c
AU Adding timer:
2015-02-06 11:24:25:933
920 111c
AU Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
2015-02-06 11:24:25:949
920 af0
DnldMgr Asking handlers to reconcile their sandboxes
2015-02-06 11:24:25:949
920 b64
Misc Microsoft signed: Yes
2015-02-06 11:24:26:154
920 b64
DtaStor Default service for AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
2015-02-06 11:24:26:154
920 b64
IdleTmr Incremented idle timer priority operation counter to 1
2015-02-06 11:24:26:154
5048 50
COMAPI - Added scan package service, ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
2015-02-06 11:24:26:154
5048 50
COMAPI -------------
2015-02-06 11:24:26:154
5048 50
COMAPI -- START -- COMAPI: Init Search [ClientId = wusa]
2015-02-06 11:24:26:154
5048 50
COMAPI ---------
2015-02-06 11:24:26:154
5048 50
COMAPI -------------
2015-02-06 11:24:26:154
5048 50
COMAPI -- START -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:26:154
5048 50
COMAPI ---------
2015-02-06 11:24:26:169
920 b64
IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 17; does use network; is not at background priority
2015-02-06 11:24:26:169
920 b64
IdleTmr Incremented idle timer priority operation counter to 2
2015-02-06 11:24:26:341
920 b64
Report *********** Report: Initializing static reporting data ***********
2015-02-06 11:24:26:341
920 b64
Report * OS Version = 6.3.9600.0.0.131344
2015-02-06 11:24:26:341
920 b64
Report * OS Product Type = 0x00000021
2015-02-06 11:24:26:357
920 b64
Report * Computer Brand = PowerSpec
2015-02-06 11:24:26:357
920 b64
Report * Computer Model = S Series
2015-02-06 11:24:26:357
920 b64
Report * Platform Role = 1
2015-02-06 11:24:26:357
920 b64
Report * AlwaysOn/AlwaysConnected (AOAC) = 0
2015-02-06 11:24:26:357
920 b64
Report * Bios Revision = 1.1a
2015-02-06 11:24:26:357
920 b64
Report * Bios Name = 1.1a
2015-02-06 11:24:26:357
920 b64
Report * Bios Release Date = 2013-08-20T00:00:00
2015-02-06 11:24:26:357
920 b64
Report * Bios Sku Number = S Series
2015-02-06 11:24:26:357
920 b64
Report * Bios Vendor = American Megatrends Inc.
2015-02-06 11:24:26:357
920 b64
Report * Bios Family = Server
2015-02-06 11:24:26:357
920 b64
Report * Bios Major Release = 4
2015-02-06 11:24:26:357
920 b64
Report * Bios Minor Release = 6
2015-02-06 11:24:26:357
920 b64
Report * Locale ID = 1033
2015-02-06 11:24:26:357
920 b64
Handler Calculating current update level for this session
[ Omitted data ]
http://support.microsoft.com/?kbid=3000850, timestamp 01d039c57a22c0be
2015-02-06 11:24:28:388
920 b64
Handler Done calculating current update level for this session
2015-02-06 11:24:28:982
920 b64
Agent *** START *** Queueing Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
5048 50
COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:28:982
920 11f4
Agent *** END *** Queueing Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
920 11f4
Agent *************
2015-02-06 11:24:28:982
920 11f4
Agent ** START ** Agent: Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:28:982
920 11f4
Agent *********
2015-02-06 11:24:28:982
920 11f4
Agent * Online = Yes; Ignore download priority = No
2015-02-06 11:24:28:982
920 11f4
Agent * Criteria = "DeploymentAction='Installation'"
2015-02-06 11:24:28:982
920 11f4
Agent * ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
2015-02-06 11:24:28:982
920 11f4
Agent * Search Scope = {Machine}
2015-02-06 11:24:28:982
920 11f4
Agent * Caller SID for Applicability: S-1-5-21-3157695610-3447843402-2534478823-500
2015-02-06 11:24:28:982
920 11f4
Agent * RegisterService is set
2015-02-06 11:24:29:185
920 11f4
PT +++++++++++ PT: Synchronizing server updates +++++++++++
2015-02-06 11:24:29:185
920 11f4
PT + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
2015-02-06 11:24:29:185
920 11f4
PT WARNING: Cached cookie has expired or new PID is available
2015-02-06 11:24:29:185
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:185
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:185
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:294
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:294
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:294
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:357
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:357
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:357
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:29:638
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:29:638
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:29:638
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:013
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:30:013
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:30:013
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:044
920 11f4
Agent Reading cached app categories using lifetime 604800 seconds
2015-02-06 11:24:30:044
920 11f4
Agent Read 0 cached app categories
2015-02-06 11:24:30:044
920 11f4
Agent SyncUpdates adding 0 visited app categories
2015-02-06 11:24:30:044
920 11f4
PT + SyncUpdates round trips: 5
2015-02-06 11:24:30:076
920 11f4
PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2015-02-06 11:24:30:076
920 11f4
PT + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
2015-02-06 11:24:30:138
920 11f4
Agent * Found 0 updates and 54 categories in search; evaluated appl. rules of 126 out of 284 deployed entities
2015-02-06 11:24:30:138
920 11f4
Agent *********
2015-02-06 11:24:30:138
920 11f4
Agent ** END ** Agent: Finding updates [CallerId = wusa Id = 1]
2015-02-06 11:24:30:138
920 11f4
Agent *************
2015-02-06 11:24:30:138
920 11f4
IdleTmr WU operation (CSearchCall::Init ID 1, operation # 17) stopped; does use network; is not at background priority
2015-02-06 11:24:30:138
920 11f4
IdleTmr Decremented idle timer priority operation counter to 1
2015-02-06 11:24:30:154
5048 1428
COMAPI >>-- RESUMED -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:30:154
5048 1428
COMAPI - Updates found = 0
2015-02-06 11:24:30:154
5048 1428
COMAPI ---------
2015-02-06 11:24:30:154
5048 1428
COMAPI -- END -- COMAPI: Search [ClientId = wusa]
2015-02-06 11:24:30:154
5048 1428
COMAPI -------------

Installing SQL Server 2014 Express package as ClickOnce prerequisite

I'm using clickOnce and deploying an installer with it.
I have tried various settings. Using SQL Server 2008 Express and SQL Server 2012 Express as prerequisite is all ok (I've dowloaded them and set the option of clickonce "download prerequisites from the same path of app").
Now I'm trying to do the same thing with SQL Server 2014 Express.
Since the SQL Server 2014 Express package isn't alredy done line 2008 and 2012 versiones, I'm trying to create it.
I have done and it seems to work, but while installing it gives error number **-2054422506**. It is a very generic error and I don't understand it.
It appears a pop up saying the installation is stopped because it is an error installing SQL Server Express 2014 and to look the log for more infos.
The log only says:
    Installing using command
    'C:\Users\VIRTUA~1\AppData\Local\Temp\VSD24F4.tmp\SqlExpress2014\
    SQLEXPR32_x86_ITA.EXE' and parameters '/q /action=Install /features=SQL
    /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is
    /sqlsvcaccount="NT Authority\Network Service'
    Process exited with code -2054422506
    Status of package 'SQL Server 2014 Express' after install is 'InstallFailed'
So, I've tried to install SQL Server 2014 Express manually, without ClickOnce, and it works. So I think I've made some mess in the xml file of the package.
My package is so build (in C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\Bootstrapper\Packages\):
    \SqlExpress2014
         \it
             SQLEXPR32_x86_ITA.exe
             SQLEXPR_x64_ITA.exe
             eula.rtf
             package.xml
         product.xml
         SqlExpressChk.exe
This is my package.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<Package
xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"
Name="DisplayName"
Culture="Culture"
LicenseAgreement="eula.rtf">
<PackageFiles CopyAllPackageFiles="false">
<PackageFile Name="SQLEXPR32_x86_ITA.EXE"/>
<PackageFile Name="SQLEXPR_x64_ITA.EXE" />
<PackageFile Name="eula.rtf"/>
</PackageFiles>
<InstallChecks>
<ExternalCheck Property="SQLExpressChk" PackageFile="SqlExpressChk.exe" Arguments="11.0.2100 1040"/>
</InstallChecks>
<Commands Reboot="Defer">

<Command PackageFile="SQLEXPR32_x86_ITA.EXE"
Arguments='/q /action=Install /features=SQL /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /sqlsvcaccount="NT Authority\Network Service"
/IAcceptSqlServerLicenseTerms /SQLSVCPASSWORD="234692Is" /SQLSYSADMINACCOUNTS="NT Authority\Network Service" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"'
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<FailIf Property="VersionNT" Compare="ValueNotExists" String="InvalidPlatformOS"/>
<FailIf Property="VersionNT" Compare="VersionLessThan" Value="6.0.0" String="InvalidPlatformOS"/>
<FailIf Property="VersionNT" Compare="VersionLessThan" Value="6.0.2" String="InvalidPlatformOSServicePack"/>
<FailIf Property="VersionNT" Compare="VersionEqualTo" Value="6.1.0" String="InvalidPlatformOSServicePack"/>
<FailIf Property="AdminUser" Compare="ValueEqualTo" Value="false" String="AdminRequired"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-1" String="InvalidUpgradeNotExpress"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-2" String="InvalidUpgradeNotExpressCore"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-3" String="InvalidUpgradeLanguage"/>
<FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-4" String="InvalidUpgradeWoW"/>
<FailIf Property="SQLExpressChk" Compare="ValueLessThan" Value="-4" String="GeneralFailure"/>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="Intel"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="1"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>

<Command PackageFile="SQLEXPR32_x86_ITA.EXE"
Arguments="/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck"
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="Intel"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="2"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>

<Command PackageFile="SQLEXPR_x64_ITA.EXE"
Arguments='/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck'
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="amd64"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="1"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>

<Command PackageFile="SQLEXPR_x64_ITA.EXE"
Arguments="/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck"
EstimatedInstalledBytes="225000000"
EstimatedInstallSeconds="420">
<InstallConditions>
<BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="amd64"/>
<BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="2"/>
</InstallConditions>
<ExitCodes>
<ExitCode Value="0" Result="Success"/>
<ExitCode Value="1641" Result="SuccessReboot"/>
<ExitCode Value="3010" Result="SuccessReboot"/>

<ExitCode Value="-2067919934" Result="FailReboot"/>

<ExitCode Value="-2067723326" Result="FailReboot"/>

<ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>

<ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>

<ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>

<ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>

<ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>

<ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>

<ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
<ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
<DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
</ExitCodes>
</Command>
</Commands>
<Strings>
<String Name="DisplayName">SQL Server 2014 Express</String>
<String Name="Culture">it</String>
<String Name="SqlExpr32Exe">http://download.microsoft.com/download/1/6/E/16E343FB-7961-457C-A9C9-E6919F2B7188/Express%2032BIT/SQLEXPR_x86_ITA.exe</String>
<String Name="SqlExpr64Exe">http://download.microsoft.com/download/1/6/E/16E343FB-7961-457C-A9C9-E6919F2B7188/Express%2064BIT/SQLEXPR_x64_ITA.exe</String>
<String Name="AdminRequired">Non si dispone delle autorizzazioni necessarie per installare SQL Server 2014 Express. Rivolgersi all'amministratore.</String>
<String Name="GeneralFailure">Errore durante il tentativo di installazione di SQL Server 2014 Express.</String>
<String Name="InvalidPlatformOS">La versione del sistema operativo corrente non supporta SQL Server 2014 Express.</String>
<String Name="InvalidPlatformOSServicePack">Il sistema operativo corrente non soddisfa i requisiti di livello di Service Pack per SQL Server 2014 Express. Installare il Service Pack più recente dall'Area download Microsoft all'indirizzo http://www.microsoft.com/downloads prima di continuare l'installazione.</String>
<String Name="InvalidPlatformOSLanguage">La versione italiana di SQL Server 2014 Express può essere installata unicamente in un sistema operativo Windows nella stessa lingua.</String>
<String Name="AnotherInstanceRunning">Un'altra istanza del programma di installazione è già in esecuzione. Per continuare, è necessario attendere il completamento di tale istanza.</String>
<String Name="BetaComponentsFailure">È stata rilevata una versione beta di .NET Framework o SQL Server nel computer. Disinstallare le versioni beta precedenti dei componenti di SQL Server 2014, dei file di supporto di SQL Server o di .NET Framework prima di continuare.</String>
<String Name="InvalidPlatformArchitecture">Questa versione di SQL Server 2014 Express non è supportata per l'architettura del processore corrente.</String>
<String Name="InvalidUpgradeNotExpress">L'istanza di SQL Server denominata 'SQLEXPRESS' non è un'istanza di SQL Server Express. Impossibile eseguirne l'aggiornamento a SQL Server 2014 Express.</String>
<String Name="InvalidUpgradeNotExpressCore">L'istanza di SQL Server Express denominata 'SQLEXPRESS' contiene componenti non inclusi in SQL Server 2014 Express. Impossibile eseguire l'aggiornamento di tale istanza in SQL Server 2014 Express. Utilizzare SQL Server 2014 Express with Advanced Services.</String>
<String Name="InvalidUpgradeLanguage">L'istanza di SQL Server Express denominata 'SQLEXPRESS' è una versione in una lingua diversa rispetto a SQL Server 2014 Express. Impossibile eseguire l'aggiornamento di tale istanza.</String>
<String Name="InvalidUpgradeWoW">Impossibile eseguire l'aggiornamento dell'istanza esistente di SQL Server Express (x64 WoW) denominata 'SQLEXPRESS' mediante SQL Server 2014 Express (x64). Disinstallare l'istanza esistente di SQL Server Express e riprovare a installare SQL Server 2014 Express (x64).</String>
</Strings>
</Package>
And this is the product.xml:
<?xml version="1.0" encoding="utf-8"?>

<Product xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper" ProductCode="Microsoft.SqlServer.Express.12.0">
<RelatedProducts>
<EitherProducts>
<DependsOnProduct Code=".NETFramework,Version=v4.5" />
<DependsOnProduct Code=".NETFramework,Version=v4.0" />
</EitherProducts>

<IncludesProduct Code="Microsoft.Sql.Server.Express.1.0" />
<IncludesProduct Code="Microsoft.Sql.Server.Express.9.2" />
<IncludesProduct Code="Microsoft.Sql.Server.Express.10.0" />
<IncludesProduct Code="Microsoft.SqlServer.Express.10.5" />
<IncludesProduct Code="Microsoft.SqlServer.Express.11.0" />
</RelatedProducts>
<PackageFiles>
<PackageFile Name="SqlExpressChk.exe" />
</PackageFiles>
</Product>
I've copied the SqlExpressChk.exe file from the SQL Server 2012 Express package, hoping it is the same (2008 and 2012 versions seems the same, so I supposed it also for the 2014).
I've delete the part in package.xml about the publicKey, since I don't know it and, further, I think I don't need it.
In the same file, I've inserted custom parameters, first like in the 2008 and 2012 versions, then doing some attempts (without success).
Did anyone have this problem? How did you have manage it?
**NOTE**: I'm using my clickOnce deploy in an empty virtual machine, so there aren't any conflicts o something similar.
More attempts, more failures, always the same error! I'm deleting the optional stuff to study better the core of the xml, but still no success.. does microsoft have a package of sql server 2014 express?

refer to this link
http://bootstrapper-manifest-generator-for-vs20.software.informer.com/2.0/
remember make the reply as answer and vote the reply as helpful if it helps.
thanks! =)
SqlServer usually runs a file (SqlExpressChk.exe) to see if there is already an installation and a sql instance called sqlExpress (for the express installations). Do you know how can do this test with the bootstrapper manifest generator?
I am not able to test it currently, but I assume that will also check whether that has installed.
You have tested it, right?
remember make the reply as answer and vote the reply as helpful if it helps.

Install SQL Server 2014 in Windows Server 2012 R2

Hi,
I had install a Windows server 2012 R2 Standard version in my VM and i make it as my domain server as well. I had create another account "ABC" and login with this new created account "ABC" in the same machine to install SQL server 2014,
it give me a warning for rule "Computer domain controller" which I understand that I'm installing the SQL server in the domain controller is not recommended. I continue to install and when reach to Server Configuration, I found that SQL Server Analysis
Service account is missing where I cannot found it.
May I know is there any features that I missing or any way to make it done?
Thank you.

I found that SQL Server Analysis Service account is missing where I cannot found it.
May I know is there any features that I missing or any way to make it done?
Thank you.
IIRC (If I remember correct)Configuring Analysis service account is after you have passed the Server configuration page. Did you selected analysis service checkbox when on feature selection page. What editoon of SQL server 2014 you are installing are
you installing express edition ? SSAS is not present in express edition
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

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!!!

SQL Server 2014 New T-SQL Features

Similar Messages

Maybe you are looking for