Using SQL Server 2012 FileTables

I like to know how to use SQL 2012 SP1 File Tables with SharePoint 2013 SP1

File tables are not supported with SharePoint content databases. SharePoint specifically just uses FILESTREAM for RBS.
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.

Similar Messages

Using SQL Server 2012 SSIS to Extract Data From SAP

Hi
What is the current best practice for using SQL Server 2012 SSIS to extract data from SAP R3? Please note we are looking for a solution that does not use SAP BW or SAP OHS.
Ideally we would like to build our ETL SSIS process to make a .NET call to an SAP RFC procedure and avoid using web services.
With SS2012 can we use any of these without using SAP BW:
- SAP .NET Connector
- MS ADO .NET
- BizTalk .NET 3.0 Adapter
Thanks and take care,
Shayne

Hi Shayne,
You can use the .NET Framework Data Provider for mySAP Business Suite along with SQL Server Integration Service (SSIS) to import data from an SAP system into SQL Server database tables, flat files, or other compatible destination types. You can create an SSIS
package that can be executed to import data from an SAP system.
You must use the SQL Server Import and Export wizard to import data into the SQL Server database. You must provide a select query to specify data to be imported. The query must confirm to the semantics supported by the Data Provider for SAP. You can start the
SQL Server Import Export Wizard either from the SQL Server Management Studio or from an Integration Service project in Visual Studio. Detail steps please see:
Importing SAP Data Using SQL Server Management Studio:
http://msdn.microsoft.com/en-us/library/cc185161(v=bts.10).aspx
Importing SAP Data Using Visual Studio:
http://msdn.microsoft.com/en-us/library/cc185254(v=bts.10).aspx
Please feel free to ask if you have any question.
Thanks,
Eileen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

Using SQL Server 2012 Express with Bitocker

Hello,
I'm currently working on getting our SQL Server Express database working with BitLocker but I am coming across a few problems. Here is my scenario:
The OS is partitioned into two volumes (C and D).
The C volume contains the OS and Software, while the D volume is primarily used for the database files (logs, back, and mdf).
The D volume is encrypted using BitLocker
The database connects using the SA account (SQL Server Authentication)
From what I understand, BitLocker must be enabled with the same account that the SQL Server is running on. So what I have done is change the SQL Server service account to the user account (lets say its called User) via SQL Configuration Manager. While staying
logged into User account, I then enable BitLocker via Control Panel -> System and Security -> BitLocker Drive Encryption. I then reboot and then while the software is trying to connect to the database I get the following exception:
'login failed for user sa'.
Is there anything I need to do to get this working? Thanks for the help.

Hi moncadad,
When you turn off BitLocker, does the database also show “Recovery Pending”? If so, the simplest cause for “Recovery Pending” might be that a disk spin-up was slow, or a disk became full. Please read this
blog to fix the issue, then check if you can successfully connect to the database after you turn on BitLocker.
However, if you are not able to view the database contents only after you turn on BitLocker, I suspect that there are some issues about configuring BitLocker. As far as I know, Bitlocker must be performed by a member of Local Admins Group, please make sure
that your account is a member of Local Admins Group on your computer.
Also I would like to recommend you post the question in the
Microsoft Bitlocker Administration and Monitoring (MBAM) forum to get better support. For more details about configuring SQL Server with Bitlocker, please review the following similar articles.
Using SQL Server 2012 Standard with Bitlocker
How can I retrieve my BitLocker recovery key from MBAM in Windows PE
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Can we use SQL Server 2012 Web Edition as a witness server in mirroring?

Hi All,
Can we use SQL Server 2012 Web Edition as a witness server in mirroring?
Grateful to your time and support. Regards, Shiva

Hi All,
Can we use SQL Server 2012 Web Edition as a witness server in mirroring?
Grateful to your time and support. Regards, Shiva
As Per BOL
We strongly recommend that the witness reside on a separate computer from the partners. Database mirroring partners are supported only by SQL Server 2005 Standard and later versions and by SQL Server 2005 Enterprise Edition and later versions.
Witnesses, in contrast, are also supported by SQL Server 2005 Workgroup and later versions and by SQL Server 2005 Express Edition and later versions. Except during an upgrade from an earlier version of SQL Server, the server instances in a
mirroring session must all be running the same version of SQL Server. For example, a SQL Server 2005 witness is supported when you are upgrading from a SQL Server 2005 mirroring configuration but cannot be added to an existing or new SQL Server 2008 or later
mirroring configuration.
A witness can run on any reliable computer system that supports any of these editions of SQL Server. However, we recommend that every server instance that is used as a witness correspond to the minimum configuration that is required for the SQL Server Standard
version that you are running. For more information about these requirements
http://technet.microsoft.com/en-us/library/ms175191.aspx#SwHwRecommendations
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

EHP2 - EHP7 Upgrade Path using SQL Server 2012/Win Server 2012 R2

Hi Guys.
I have question regarging Upgrade Roadmap for a ERP 6 EHP2 system based on NW 7.01 which I would like to Upgrade to ERP6 EHP7 SP7
Source System is
Windows 2012
SQL Server 2008 R2
EHP2 for ERP 6.0 SPS Level 14
Target System
Windows 2012
SQL Server 2012
EHP7 for ERP 6.0 SP 7 based on NW 7.4 SP 9
During Upgrade checks it says I must Upgrade Database first before continue since DB Release is too low for NW 7.4 SP9 as stated in Note
1951491 - Minimal DB system platform requirements for SAP NetWeaver 7.4 SP08
So, at this point I agree i have to update SQL Server to 2012 before next step
Now, my concern is that my Source System does not have the minimum NW SP level (14) to run under SQL Server 2012 which is 26.
Im currently running SAP Kernel 721 EXT Level 401 which is above mininum
According to Note 1651862 - Release planning for Microsoft SQL Server 2012 that would not be possible
Existing systems of SAP products that are out of SAP maintenance can be upgraded to SQL Server 2012 in order to prepare a SAP upgrade, if they match the SAP NetWeaver Support Package requirements defined below.
SAP products prior to SAP NetWeaver 7.0 are not supported at all on SQL Server 2012.
Required minimum SAP Netweaver Support Package Stacks (SPSs) for SQL Server 2012 (SAP ABAP, SAP ABAP+JAVA stacks)
SAP NETWEAVER 7.0 - SPS 26 (SAP BASIS 26, SAP BW 28)
SAP EHP1 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP2 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP3 FOR SAP NETWEAVER 7.0 - SPS 03 (SAP BASIS 03, SAP BW 03)
SAP NETWEAVER 7.1 - SPS 14 (SAP BASIS SP14)
SAP EHP1 FOR SAP NETWEAVER 7.1 EhP1 - SPS 10(SAP BASIS SP10, SAP BW SP10)
SAP NetWeaver 7.2 - no restriction
SAP NETWEAVER 7.3 - SPS 07 (SAP BASIS 07, SAP BW 07)
SAP EHP1 FOR SAP NETWEAVER 7.3 - SPS 03 (SAP BASIS 03, SAP BW 03)
If your system is running on a SPS lower than the one required above, you have to apply the minimum required SPS before upgrading/migrating to SQL Server 2012.
If you install a NetWeaver product on SQL Server 2012, the required SPS for your product must be applied immediately after the installation - see SAP note 1676665, section I for more information.
But performing the Upgrade would be technically possible? I mean not for productive use but technicaly during that time the Database is Upgrade and during SUM Execution.
According to the note it states if you install a Netweaver Product in SQL Server 2012, SPS must be applied immediately, so is kinda ambigous what SAP is saying.
Best
Martin

Hi Martin,
For a test scenario, there's no harm in trying it (other than spending a lot of time on it, but hopefully that will prove not to be a waste). Generally, I expect you'll be fine upgrading your DBMS even though you aren't on the required minimum SP yet. The main thing you'll be missing out on is the updates to DBACOCKPIT, but once you do your EhP upgrade (with sps update included), you'll be putting that in place.
So, you could try this on your sandbox system and see if there are any problems. I assume the intent is to start the EhP upgrade as soon as the DBMS upgrade is done, right? In other words, you won't be actually using the system without the required SP except to run the EhP upgrade?
Alternatively, you could do a minimal support pack update, perhaps just a Basis SP only, to the minimum SP needed for your current release, then do the DBMS upgrade, then proceed with the EhP upgrade. This would be the safest procedure, but, as I said, I expect you can probably get away without going to this level without much problem. Again, the idea would be minimizing the time between the start and end of the total project on each system (DEV, QAS, PRD, etc).
Regards,
Matt

Not able to use Sql Server 2012 Intellisenese

I am not able to use Sql Server Intellisence .
I refer following links
http://blog.sqlauthority.com/2009/03/31/sql-server-2008-intellisense-does-not-work-enable-intellisense/
http://www.mssqltips.com/sqlservertip/2591/troubleshooting-intellisense-in-sql-server-management-studio-2012/

Hi,
Check the below link. Hope it helps
http://msdn.microsoft.com/en-us/library/ms173434(v=SQL.110).aspx
You need to refresh it if at all you have created new schema and added tables to it. Go to the editor pane in SQL Server Management Studio, and press CTRL+SHIFT+R.
Regards, PS

Sharepoint 2007 using sql server 2012 database server

We still have an old SharePoint 2007 farm that runs on SQL Server 2008 and Reporting Services 2008. I would like to migrate this app over to SQL Server 2012. From what I gather SharePoint 2007 supports SQL 2012 if you are running WSS service pack 3 and
SharePoint server service pack 3 I am already on SP3. So my question is who all here is running SharePoint 2007 on SQL 2012 and have you had any problems?

Yes I have an environment that is SPS 2007 wSP3 and SQL Server 2012, and have been doing this for 2 months. So far, no problems. There have been issies with User Profile services, but those turned out to be unrelated.
Kind regards,
Margriet Bruggeman
Lois & Clark IT Services
web site: http://www.loisandclark.eu
blog: http://www.sharepointdragons.com

SQL Server 2012 - Cannot Use Network Drive as a Backup Device

Hello Community,
I am using SQL Server 2012 and I am trying to add a mapped drive as a backup device, but I am not even to see that drive from SQL Server. Has anyone else had this issue and if so can you help me resolve it?
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

Hey David,
I checked the drive and share permissions, and the service account for SQL Server, in this case named "sqlsvc" has been granted full permission to both. I tried the script but it also failed, the code is below:
DATABASE[TestDb]TO
DISK=N'\\sqlclus02\SharePointBackup\TestDb.bak'WITHNOFORMAT,NOINIT,
NAME=N'TestDb-Full
Database Backup',SKIP,NOREWIND,NOUNLOAD,
STATS=10
Also, I haven't been able to confirm that the sqlsvc account is a domain account, but I do know the server is clustered.
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

Unable to add replication feature in sql server 2012 web edition

Hi All,
We are using SQL Server 2012, Web edition and when it was installed replication is not an added feature so I tried to add this feature but getting below error.
Error: There are no SQL Server instances or shared features that can be updated on this computer.
Description: The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update. The installed SQL Server product version is 11.1.3000.0, and the expected SQL Server version is 11.0.2100.60
And also please let me know how to identify the default file location of the setup file 'setup.exe' for SQL Server 2012 (Webedition, 64bit) Grateful to your time and support.
I'm using "C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2777772\QFE\setup.exe" to add replication feature, please correct me if I'm wrong.
Thank You.
Regards,
Kalyan
----Learners Curiosity Never Ends----

It looks like you are trying to add Replication Components, however, you are using the Cumulative update package 5 setup, which is wrong.
Note that you will not find the setup file for SQL Server on your file system, it will be on your installation media.
To install SQL Server Replication Components, locate your installation media and run Setup.exe. Select the add features to an existing instance option, select your instance, and add replication components.
Brandon Williams (blog |
linkedin)

Getting error while expanding SQL Server 2012 agent.

Hi All,
Server Version Details: Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
   Oct 19 2012 13:38:57
   Copyright (c) Microsoft Corporation
   Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
We are using SQL Server 2012 in Active/Passive Cluster and the problem is getting below error while expanding SQL Agent. Please share you views on this. Thank You.
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
A severe error occurred on the current command. The results, if any, should be discarded. (Microsoft SQL Server, Error: 0)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.3000&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476
BUTTONS:
OK
Regards,
Kalyan
----Learners Curiosity Never Ends----

Hi OHM SAI RAM,
I’m writing to follow up with you on this post. Was the problem resolved after checking the error message and performing the action plan steps? I’d like to mark this issue as "Answered". Please also feel free to unmark the issue, with any new findings or
concerns you may have.
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
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: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
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\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
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\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\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: SQL Server Data Tools
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Run Reporting services 2005 with databases housed on SQL Server 2012?

Hi, I have a RS 2005 install in which the ReportServer and ReportServerTempDB databases reside on a different SQL Server 2005 server. I am planning to upgrade DB server to 2012 and would like to keep SSRS as 2005.As a second phase I will upgrade SSRS2005
to SSRS 2008. So I would be running something like this:
Server A: SQL 2005 Reporting Services
Server B: SQL 2012 database engine - housing ReportServer and ReportServerTempDB
Is this configuration supported?

Hello,
According to the
BOL, Report Server service checks the database version at startup. If the report server is connected to a database that is an earlier version, the report server will update the database during startup.If you have a newer report server database, you
cannot use it with an earlier version of a report server instances.
In that case, the earlier versions of SQL Server Database Engine that can be used to host the SSRS report server databases. For example, In SQL Server 2005 Reporting Services, we can use either SQL Server 2000 or SQL Server 2005 to host the databases, for
SSRS 2012, we can use SQL Server 2012,2008 R2,2008,2005.
Based on my test, In the Reporting Services 2005 Configure Manager, we can create a new database on a remote SQL Server 2012 database engine and the Initialization is successful.
In this way, the databases are created from the script file which installed with the Reporting Services instance, you can find the Catalog.sql and CatalogTempDB.sql under folder C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer.
However, when upgrade the existing ReportServer database and ReportServerTempDB database on the SQL Server 2012 by restore from a backup, we cannot use this existing database for Reporting Services 2005 and get the following message:
The database version (162) does not match your reporting serivces installation.And the initialization failed.
In your case, you can host the ReportServer database and ReportServerTempDB database of SSRS 2005 on SQL Server 2012 database enginer by create a new database from Reporting Services 2005 Configure Manager. But you cannot use the existing
database which upgrade to SQL Server 2012.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

SharePoint 2010 and SQL Server 2012 issue

Hi,
I have SharePoint 2010 integrated with SQL Server 2008 R2 in my machine. I wanted to use Power View feature, so I went for SQL Server 2012 installation. Now when I try to create the SQL Server Reporting service service application, it says, this feature
is not supported by current version of database.
Please let me know how to fix the issue. Do I need to reinstall SharePoint 2010 once again using SQL Server 2012 ?
thanks
Tarique

http://social.technet.microsoft.com/Forums/sharepoint/en-US/9eacbd00-f264-4f55-bd27-55cf0761cbd7/power-view-is-not-supported-in-this-edition-of-reporting-services?forum=sharepointadmin
The only requirements for SSRS Integrated mode/PowerView are that you're using SharePoint Enterprise and SQL Enterprise/BI and that SharePoint be installed and joined to the farm on the server where you're also installing SSRS.
You need to reconfigure your sharepoint farm farm to use SQL server 2012
http://technet.microsoft.com/en-us/library/ee210640.aspx
Business intelligence features are not all available in all editions of SQL Server 2012

SQL Server 2012 BI Features (Standart Edition)

Hello everyone
I've a question about licensing in SharePoint and SQL Server. Firstly, we are using SharePoint 2013 Enterprise edition and SQL Server 2012 Standart edition. Which of tools below are possible use integrated with SharePoint 2013 with our current
SQL Server Edition?
-PowerView
-PowerPivot
-SSRS
Also, is it possible to Analysis services intensively with our SQL server Standtart edition? For instance, creating cubes,data mining, forecasting, etc.. ?
Thanks in advance..

Hi Omnipotent06,
Reporting Services in SharePoint mode is a collection of server components that provide report generation and delivery, based on Microsoft SQL Server and Microsoft SharePoint products. But different features are supported by the different
editions of SQL Server 2012. If we are using SQL Server 2012 Standard edition, there are many limitations. For example, Power View and PowerPivot are not supported in SQL Server 2012 Standard edition.
It supports most features of Reporting Services, except Data driven report subscription, Scale out deployment(Web farms) and Alerting. As to Analysis Services, it supports Backup/Restore, Attach/Detach databases, High Availability and
Programmability (AMO, ADOMD.Net, OLEDB, XML/A, ASSL) features. For more details, please see the following document:
http://technet.microsoft.com/en-us/library/cc645993.aspx
The following excellent article is for your reference:
Installing Reporting Services SharePoint Mode Report Server for Power View and Data Alerting
Hope this helps.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Package migration from SSIS 2008 R2 to SQL server 2012

hi guys:
My company has decided to use Sql server 2012 for the database service, Integration service as well as analysis service
The first question is which tool I should install to run packages ? in SQL Server 2008 R2, I've installed BIDS which is inside the disk.
Also do I need to install any visual studio tools? I was under the impression that the BIDS 2008 was using kinda shell visual studio.
Thanks
Hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Hi cat_ca,
To develop package in SQL Server 2012 Integration Services, we use the SQL Server Data Tools (SSDT 2012) which can be installed from the SQL Server 2012 install media. The SSDT 2012 use Visual Studio 2010 shell by default and can be integrated into Visual
Studio 2010. By installing SQL Server Data Tools - Business Intelligence for Visual Studio 2012, we can also integrate SSDT 2012 into Visual Studio 2012. However, SSDT 2012 cannot be integrated into Visual Studio 2013. As far as I know, the SSDT 2014 released
in SQL Server 2014 RTM will use the Visual Studio 2013 shell and can be integrated into Visual Studio 2013.
Regards,
Mike Yin
TechNet Community Support

Using SQL Server 2012 FileTables

Similar Messages

Maybe you are looking for