SQL 2008 to 2014

Hi
I have 2008 std and 2014 std installed side by side on the same server. How do I migrate 2008 dbs to 2014 so they are also upgraded to 2014 db format?
Thanks
Regards

Hello,
You can perform backup/restore and detach/attach methods.
https://msdn.microsoft.com/en-us/library/ms187510.aspx
https://msdn.microsoft.com/en-us/library/ms177429.aspx
https://msdn.microsoft.com/en-us/library/ms189625.aspx
You can use the following article to transfer SQL Server logins, if needed.
http://support.microsoft.com/kb/918992
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

SQL 2008 and 2014 side by side

Hi
I have 2008 std (instance DB-SERVER) and 2014 std (instance DB-SERVER\SQL2K14) on the same machine side by side. I am trying to configure tcp/ip for the 2014 to be able to access it remotely over LAN. In Configuration Manager for tcp/ip setup I have used
the same default port 1433 for both instances. Problem is this makes one of the instances to fail to start with error;
Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
What is the correct way to configure both instances so both are accessible over LAN via tcp/ip?
Thanks
Regards

Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)
Cheers,
Saeid Hasani
Database Consultant
Please feel free to contact me at [email protected] as well as on Twitter and Facebook.
[My Writings on TechNet Wiki] [T-SQL Blog] [Curah!]
[Twitter] [Facebook] [Email]

Install SQL Server Express 2014 on same machine as SQL Server Express 2008 R2

Hello, I have a customer with a CRM application using SQL Server 2008 Express (installed as part of the product installation).
They wish to use another database-based application and the CRM company is recommending a separate instance of SQL for the other database.
So, I am wondering if it is possible to install SQL Server Express 2014 on the same machine as the existing SQL Server Express 2008 R2?
Many thanks for any assistance provided.

The CRM application in question is SAGE Act!. It is their own (proprietary) application.
I am less interested in comparability questions concerning this application than I am about the possibility of installing
SQL Server Express 2014 or creating another database instance within the existing SQL Server Express 2008.

Linked server issue using SQLNCLI versions on SQL 2008 & 2014

Hi all,
Our product creates databases on a sql server 2008 instance and creates linked servers between them to use distributed queries.
This looks like: "EXEC sp_addlinkedserver 'linkDatabaseA', '', 'SQLNCLI10', '.', NULL, NULL, 'DatabaseA'"".
Distributed queries from second database to DatabaseA work fine in this scenario.
As we want to support both SQL 2008 and SQL 2014 in the next product version, I changed this to SQLNCLI11 as the provider
and tested on SQL 2008 after installation of the SQLNCLI11 driver.
This resulted in following error message:
Msg 468, Level 16, State 9, Line 7
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
This is very suprising as the SQL Server 2008 instance and both DB's have "SQL_Latin1_General_CP1_CI_AS" as their collation sequence.
Then I tried the opposite, installing SQLNCLI10 on SQL 2014. This gave exactly same error! Using SQLNCLI11 went fine ofcourse.
Generation sp_addlinkedserver statements with correct driver based on SQL version, I'd rather not do (some of the calls are
generated in SQL from settings in other db tables which are also used for external connx) and adding COLLATE to the queries also
has consequences like performance degradation. Adding collate on SQL 2014 with SQLNCLI10 as linked server provider results in
following error:
Msg 7399, Level 16, State 1, Line 1617
The OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA" reported an error. Access denied.
Msg 7301, Level 16, State 2, Line 1617
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA".
Q: Is there any way that SQLNCLI11 can be made to work for linked servers on SQL2008 (preferred solution) or SQLNCLI10 on SQL2014?
Thx for any feedback.
Regards, Jouke

Hi Sofiya,
Thx for replying.
For the deployment reasons mentioned above, I would prefer to use only one SQLNCLI version in both 2008R2 & 2012/2014 scenario's. Most preferred would ofcourse be SQLNCLI11 as this is the latest.
This would mean that I'd like to be able to configure linked server in SQL2008R2 using SQLNCLI11 driver.
I would expect that it would be downward compatible with SQLNCLI10 for all client usage, including linked server, which in essence is one SQL DB doing client access to another SQL DB either on same server instance or another. I suspect it requests DB
metadata from remote DB in order to make decisions and this seems not to work in my setup. If this metadata API is part of the public API, this could indicate that medadata API has been broken in SQLNCLI11 (heavy speculation on my part here!), which could
also affect other usage (eg. linked server between SQL2008(R2) and SQL2012/2014 instances, (I'll try to set this up and test this, might take a few days. If someone is volunteering, below are db table schemes and query, update @datasrc to point to remote sql
server instance)).
Regards, Jouke
-- This script to run on SQL2008(R2). On SQL2012/2014, install SQLNCLI10 and change @provider in sp_addlinkedserver call.
-- Pre:
-- - DatabaseA and DatabaseB are created manually in SSMS
-- - SQLNCLI11 has been installed
USE [DatabaseA]
GO
CREATE TABLE [dbo].[DatabaseATable](
[IdField] [int] NOT NULL,
[LinkField] [nchar](10) NULL,
CONSTRAINT [PK_DatabaseATable] PRIMARY KEY CLUSTERED
[IdField] ASC
) ON [PRIMARY]
GO
EXEC master.dbo.sp_addlinkedserver @server = N'linkDatabaseA', @srvproduct=N'',@provider=N'SQLNCLI11', @datasrc=N'.', @catalog=N'DatabaseA'
GO
USE [DatabaseB]
GO
CREATE TABLE [dbo].[DatabaseBTable](
[IdField] [int] NOT NULL,
[LinkField] [nchar](10) NULL,
CONSTRAINT [PK_DatabaseBTable] PRIMARY KEY CLUSTERED
[IdField] ASC
) ON [PRIMARY]
GO
SELECT b.*, a.*
FROM DatabaseBTable AS b WITH(NOLOCK)
JOIN linkDatabaseA.DatabaseA.dbo.DatabaseATable AS a
ON a.LinkField = b.LinkField
Hi Jouke Numan,
According to your description, I install SQL Native Client 11.0 OLE DB Provider in SQL Server 2008R2, and as you post, create two database on the same instance with collation in server default, then create Linked Server with SQLNCI11.0.
When I run the query statement, it can execute well. It also do not occur the collation conflict. I still recommend you check the collation of server, database, or column and so on.
SQL Server Native Client 11.0 provides OLE DB support to applications connecting to SQL Server versions 2005, 2008, 2008R2, 2012. So for the deployment reasons, you can choose the only SQLNCLI11.0 in both SQL Server 2008R2 and SQL Server 2012/2014.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL 2014 license for SQL 2008

Hi,
I'm purchasing SQL 2014 license.
Can I use the SQL 2014 license for SQL 2008 or 2012.
Thanks,
Sathish
Sathish

Hi Sathish,
For more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the
Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Regards,
Elvis Long
TechNet Community Support

Issue With Report Builder After Installing SP3 for SQL 2008 R2

Hello. We are experiencing an issue with Report Builder 3.0 since installing SP3 for SQL 2008 R2 over the weekend. You can no longer launch Report Builder from the Reporting Services URL (http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
Application url   :
http://dicomweb/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity  : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
Application Identity  : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
  + File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [10/15/2014 9:35:56 AM] : Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application has started.
* [10/15/2014 9:36:29 AM] : Processing of deployment manifest has successfully completed.
* [10/15/2014 9:36:29 AM] : Installation of the application has started.
* [10/15/2014 9:36:31 AM] : Processing of application manifest has successfully completed.
* [10/15/2014 9:36:35 AM] : Found compatible runtime version 2.0.50727.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [10/15/2014 9:36:43 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification
notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Hi DMcGarveyt,
This is an known issue in SSRS 2008 R2 SP3. For this issue, Microsoft has published an article addressing this issue. It is not planning to release a fix for this defect. But there's workarounds for this issue. Please refer to the link below:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

SharePoint 2010 + SQL 2008 + DPM 2012 Backup Failures

I have a single SharePoint 2010 WFE and a SQL 2008 server backend. Since configuring DPM to run the SharePoint backup through the WFE, I have had no success with backups.
DPM Reports:
The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError: The writer experienced a non-transient error. If the backup process
is retried, the error is likely to reoccur. (0x800423F4))
Event Log on SQL Server Reports:
Log Name:      Application
Source:        SQLWRITER
Date:          4/24/2014 4:44:17 PM
Event ID:      24583
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf
' is too long. Maximum length is 259.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SQLWRITER" />
    <EventID Qualifiers="0">24583</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293470</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
</System>
<EventData>
    <Data>ICommandText::Execute</Data>
    <Data>0x80040e14</Data>
    <Data>SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf
' is too long. Maximum length is 259.
</Data>
    <Binary>53514C434F4E4E43313236330000000053514C434F4E4E433132323800000000</Binary>
</EventData>
</Event>
Followed by:
Log Name:      Application
Source:        VSS
Date:          4/24/2014 4:44:17 PM
Event ID:      8229
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
   PostSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8229</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293471</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
</System>
<EventData>
    <Data>0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
</Data>
    <Data>
Operation:
   PostSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036</Data>
    <Binary>2D20436F64653A20575254575254494330303030353239392D2043616C6C3A20575254575254494330303030333336352D205049443A202030303030363033362D205449443A202030303030323630342D20434D443A202022433A5C50726F6772616D2046696C65735C4D6963726F736F66742053514C205365727665725C39305C5368617265645C73716C7772697465722E65786522202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
When I run vssadmin list writers after the error, the "SqlServerWriter" show a State of [11]. I can restart the service and the error clears up showing stable, but the next time I run the backup it fails again.
From the error, it almost sounds like the path is too long. This doesn't totally make sense to me considering the database was successfully backed up before I tried to back it up as a SharePoint database.
Any suggestions would be appreciated.

Got the issue solved.
DPM has issues with DNS Aliases for SQL.
To get this issue sorted out i used the old HOSTS file to point the right name to the right SQL server.

SQL Server Express 2014 Installation Completes with Failures and Repair Does Nothing to Help

I am attempting to install SQL Server Express 2014 on a development machine and as usual old versions of SQL and the remnants of them are a plague to the installation.
I have used to Revo Uninstaller to scrub the old installations and with my first attempt after some additional work on the registry I was able to get an instance to install and remarkably I was able to connect to the instance. However, I removed an application
reference to SQL Server 2008 after the SQL Express 2014 installation (through Control Panel > Programs > Programs and Features) and it stopped working immediately.
So I removed (uninstalled using Revo Uninstaller) every reference to any SQL Server application as well as removed all of the registry references (using Revo) and I can now install SQL Server Express 2014 with
"Feature" failures [Reporting Services, Database Engine Services, Full-Text and Semantic Extractions for Search and SQL
Server Replication] and of course it doesn't work.
Now when I attempt "Repair" the installation the process ends normally (no errors) and reports "Success" however SQL still has no instance and the services are not running nor are they visible when I open the "SQL Server Configuration
Manager".
This is the "Repair" log:
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Start time: 2014-12-21 17:21:37
End time: 2014-12-21 17:29:10
Requested action: Repair
Machine Properties:
Machine name: EDWARD-PC2
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: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2014 Management Tools - Basic 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Management Tools - Complete 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Connectivity 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Backwards Compatibility 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools SDK 1033 Express Edition 12.0.2000.8 No Yes
SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Edward\Downloads\SQLEXPRADV_x86_ENU\x86\setup\
Installation edition:
User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
UIMODE: AutoAdvance
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\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 Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\SystemConfigurationCheck_Report.htm
However this is what the "SQL Sever Configuration Manager" look like:
Why does this appear to not be working properly? I can not connect the the "local" instance and I would guess that the service either does not exist or is not running.
Edward Walker

Hello,
To my knowledge, Revo is not a supported way to uninstall SQL Server.
Please try to uninstall all you can using Control Panel -> Programs and Features, then perform a manual uninstall to
remove remnants. Try the following procedure:
1. Uninstall all SQL Server 2012 components you can using Control Panel -> Programs and Features
2. Backup the registry.
3. Delete the following keys in regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing
SQL Server.
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer like C:\Program Files\Microsoft SQL Server and subfolders.
After performing above procedure, try to reinstall SQL Server again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to install and use sql server express 2014 with tools

I am a student and have an assignment that requires I use either mysql or sql server, so I chose to download and install sql server express 2014 with tools, but after installation was complete all I can see is sql server 2014 import and export data (64-bit)
and I have no clue what to do wiith it...I had used sql server 2008 a couple of years ago and it was easy, but this is very complicated, I have been trying to get this done for 2 days now, so someone please help me and tell me what I am doing wrong.

Hi,
It seems you did not installed complete software. Make sure you have downloaded below from
SQL Server Express Download link
Express with Advanced Services (SQLEXPRADV) when you click on Get started button on page displayed by clicking on above link. This download includes Sql Server Management Studio as well.
Before moving I would Like you to first read
Hardware and Software requirements
Please refer
how to install SQL server 2014 express
Above Link is for Enterprise edition but you can use it for express as well. When you reach page feature selection please select all features to install.
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

Sharepoint 2010 SQl 2008 r2 Reporting Services Integrated with Claims

i have a 4 server sharepoint 2010 farm all servers are windows 2008 r2 x64
two severs are sharepoint app/wfe servers
one server is SQL sharepoint content db server sql 2008 r2 enterprise
one server is SQL Claims Provider DB and reporting services on SQL 2008 r2
the site is behind a forefront tmg proxy firewall for both internal and external users and both locations are producing the same results.
the web application i am having an issue with consists of a primary web app claims enabled web app that only has NTLM enabled, with an extended extranet webapp that supports claims and NTLM.
there is surrently a site collection that has been configured for reporting services when i log into the site as a SQL Claims user i am able to run the reportbuilder as a content type using the New Report builder report content type from a library on
this site. Reportbuilder launches and i am once gain prompted to login i login with the same credentials i used to log into the site and reportbuilder opens up and then i am able to open datasourceas and reports.
When i log in to the same site collection as a domain user i am able to log in to the site and launch reportbuilder. When reportbuilder opens up i am prompted to log in, i insert my domain\username and password and nothing happens the login prompt appears again
blank on the back end it throws the following exceptions
1. Password check on 'username' generated exception: 'System.ServiceModel.FaultException`1[Microsoft.IdentityModel.Tokens.FailedAuthenticationException]: The security token username and password could not be validated. (Fault Detail is equal to Microsoft.IdentityModel.Tokens.FailedAuthenticationException:
The security token username and password could not be validated.).'.
2.An exception occurred when trying to issue security token: The security token username and password could not be validated.
any thoughts on where i should begin troubleshooting this.

I think i am getting close i am now seeing a new error it seems that the sp farm account is unable my domain account when launching reportbuilder.
vent code: 4006
Event message: Membership credential verification failed.
Event time: 4/6/2014 10:59:05 AM
Event time (UTC): 4/6/2014 2:59:05 PM
Event ID: 7640af98dab846829f78e7d74a4e1e8a
Event sequence: 9
Event occurrence: 8
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/SecurityTokenServiceApplication-1-130412687342754349
    Trust level: Full
    Application Virtual Path: /SecurityTokenServiceApplication
    Application Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken\
    Machine name: (SP WFE MACHINE NAME)
Process information:
    Process ID: 8044
    Process name: w3wp.exe
    Account name: (SP FARM ACCOUNT)
Request information:
    Request URL:
    Request path:
    User host address:
    User:
    Is authenticated: False
    Authentication Type:
    Thread account name: (SP FARM ACCOUNT)
Name to authenticate: (doamin account launching reportbuilder)
Custom event details:

SQL Server 2012/2014 DBA

Hi, I have been working as system engineer for almost seven years. My primary focus is on Windows Server 2008 R2/2012 R2 technologies, Exchange Server 2010/2013, PowerShell (v2, v3 and v4), SCCM/SCOM 2012 R2, MDT 2012 U1/2013, IIS 8/8.5 and list goes on
with no MS technologies like Symantec (AV, backup products) and vSphere 5/5.5 since I am big fan of most of these technologies (honestly I am not thrilled working with Exchange Server - too much things under the hood just to send an email :-)). I
have recently decided to also dig deep into SQL Server 2012/2014 although in my company we do not have anyone whose job is primarily working as SQL DBA. Knowing that SQL Server 2012/2014 has SSRS, SSIS and SSAS beside the main
one Database Engine, I would like to find out whether SQL DBA has to know very well these three SQL components or he/she should be focused on administering SQL Server databases and querying SQL server (in case of SQL Server
2012 areas covered by exams 70-462 and 70-461). Having deep knowledge of all these SQL Server services seems like mission impossible and honestly I do not think anyone could master SQL Server "as whole" - unless, maybe, that person is working only
and I repeat only with SQL Server. It looks like SC 2012 R2 suite - mastering all products in this suite is impossible. So what should I do?

SSIS was mentioned as very powerful tool in DBA arsenal for automating many administrative tasks without too much difficulties. Since I have no experience in working with SSIS how tough is it for learning and mastering and what books/videos do you
recommend?
SSIS is a must for a DBA. In case you have questions, there is an excellent SSIS forum:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlintegrationservices
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

SQL Reporting Services 2014, Enabling Kerberos causes report manager to be extremely slow

We are migrating our environment from SQL Reporting Services 2008 to 2014 on a new server. We are currently using kerberos on the 2008 instance, but when I enable kerberos on the 2014 Reporting Services instance the Report Manager becomes extremely slow.
Has anyone seen this before? Any ideas of what I can check to see what is causing this problem.

Just to clarify it is not slow when I run a report, it is slow in general. From first load to accessing a folder, settings, etc. This is all before even executing a report.
The error I see while using Wireshark is KRB Error: KRB5KDC_ERR_BADOPTION NT Status: STATUS_NO_MATCH. When I drill down the into the
error I can see the kerberos string is testprjmnmtreports14.company.com, which is the URL we are using to access the site. I made sure to add that name as an SPN for the service account that is running SQL Reporting Services, however I still receive the error.
Then I tried configuring the site to run without a hostheader, so I accessed the site with the server name ECTSTSQLRS5 and the site works perfectly fine, no errors are reported either. So it seems I have isolated the issue down to Kerberos but I am not sure
how to resolve it. Here is some more information about my environment:
DNS/URL used: testprjmnmtreports14.company.com
Server Name (FQDN): ECTSTSQLRS5.company.int
AD Domain Name: company.int
Server Version: Windows Server 2012 R2
AD Functional Level: 2008 R2
I also have the following SPNs set for my SQL service account:
http/testprjmngmtreports14.company.com
http/testprjmngmtreports14
http/ECTSTSQLRS5.COMPANY.INT
http/ECTSTSQLRS5
As you can see I am trying to use a .com address but my AD domain is .int which I think is the issue, but I do not have the same problem on my other server that is running Windows Server 2008 R2.

SQL 2008 R2 In-Place Upgrade or Fresh Install to SQL2104

We have a server running Windows 2008 R2 and SQL 2008 R2 currently. We will call it SQL01. This houses databases for about 8 different applications and also has the name hard coded into a lot, I repeat, a lot of various things.
We are at the point where one of our applications needs to be upgraded and it only works with SQL 2014. So we need to either do an in-place upgrade or fresh install.
The obvious choice to me as a system admin is to do a fresh install, but the development side of the department knows how many places the name "SQL01" is hard coded and they want to do an in-place upgrade to avoid all the issues that would show
up if we changed names.
I have several questions, and I'd appreciate that the answers address them all if possible.
1. What are people's experiences with in-place upgrades from SQL 2008 R2 to SQL 2014?
2. To avoid this naming and coding issue, do companies use a permanent alias for their SQL servers? Like with exchange, we have an alias or A record pointing "mail" to the current Exchange server. As we do upgrades and the Exchange
server names change, the "mail" entry will always be pointed to the current one. Do people do this for SQL as well to avoid our issue of hard coding names?
3. I've head that you can also have both SQL 2008 R2 and SQL 2014 on the same server running together. This really doesn't help though if the SQL 2014 instance would need to be something other than the default which everything is currently pointed
to correct?
4. Is there any advice about a better way to go about this? Or a better way to do this moving forward? Other than not hard coding which I can't change now?
Thanks!

Hello,
Adding to the answers provided above, please consider discontinued features no longer available on SQL Server 2014.
I often see company configuring SQL Server aliases when installing SQL Server on SharePoint environments. You can certainly use DNS or use the following article.
http://msdn.microsoft.com/en-us/library/ms190445.aspx
An in-place upgrade is easier but is difficult to rollback in case something goes wrong. Meanwhile, a side-by-side upgrade provides you more control over what is upgraded, it keeps the legacy server online during the upgrade allowing you to easy rollback if
needed, but is not an automated process and the instance will not keep the same name, requiring you to use aliases or other ways to avoid client redirection.
Since you cannot change the application, go for a side-by-side upgrade and try the DNS alias or the client-side alias as I provided the procedure above.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2008 R2 Management Tools Install Fails - The specified account already exists

Hello,
The installation SQL 2008 R2 Management Tools on a Windows 7 workstation fails with the error, The specified account already exists.
Below is the Summary Log.
Thanks.
Paul
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068052700
Exit facility code:            1212
Exit error code:               1316
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time:                    2014-10-20 09:02:16
End time:                      2014-10-20 09:05:57
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\sqlncli_Cpu64_1.log
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  WS287
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:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:
\\SRVDIA18\MSSQL2008R2Install\x64\setup\
Installation edition:          STANDARD
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 <empty>
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
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:                    <empty>
INSTANCENAME:                  <empty>
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 <empty>
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141020_085102\SystemConfigurationCheck_Report.htm
The specified account already exists

There is definitely more amusing endeavours in this world, than trying to understand why an SQL Server install failed. The log files are verbose - but somehow the real information about what went wrong seems to be hiding. Never have proverb about not being
able to see the forest for all the trees felt more appropriate.
Nevertheless, this is where things go sour:
MSI (s) (F4:EC) [09:04:15:744]: Resolving source.
MSI (s) (F4:EC) [09:04:15:744]: Resolving source to launched-from source.
MSI (s) (F4:EC) [09:04:15:744]: Setting launched-from source as last-used.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourceDir property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is '\\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\'.
MSI (s) (F4:EC) [09:04:15:744]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{2180B33F-3225-423E-BBC1-7798CFD3CD1F}'.
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR ==> \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\
MSI (s) (F4:EC) [09:04:15:744]: SOURCEDIR product ==> {2180B33F-3225-423E-BBC1-7798CFD3CD1F}
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: CryptAcquireContext succeeded
MSI (s) (F4:EC) [09:04:15:744]: Determining source type
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 2203 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi 3: -2147287038
MSI (s) (F4:EC) [09:04:15:744]: Note: 1: 1316 2: \\server\MSSQL2008R2Install\1033_ENU_LP\x64\setup\x64\SQL ODBC Native Client 10 - 64bit.msi
MSI (s) (F4:EC) [09:04:15:744]: SECREPAIR: Error determining package source type
MSI (s) (F4:EC) [09:04:15:744]: SECUREREPAIR: SecureRepair Failed. Error code: 524F91D34B8
MSI (s) (F4:EC) [09:04:40:775]: Product: Microsoft SQL Server 2008 R2 Native Client -- Error 1316. The specified account already exists.
What account? I supposed you have already asked yourself that and just shaken your head.
But there is another error code 2203, NET HELPMSG 2203 says "The password parameter is invalid." And I note that the source is apparently on a share.
So where is my guess: the MSI installer - which runs as a service, somehow does not have permissions to read the installation from the share. Or is trying to log on to the share with your username/password? No, I don't know, I am just speculating widely.
But my advice would be to copy the installation directory from the share to a local disk.
Maybe that CryptAcquireContext is significant as well - I don't know.
Oh, wait, here is something just before the section above in the log:
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2205 2: 3: Environment
MSI (s) (F4:EC) [09:04:15:729]: Note: 1: 2228 2: 3: Environment 4: SELECT `Name`,`Value` FROM `Environment`,`Component` WHERE `Component_`=`Component` AND (`Component`.`Action` = 1 OR `Component`.`Action` = 2)
Action start 9:04:15: WriteEnvironmentStrings.
2205 is "The logon processor did not add the message alias." I see that in a successful log that I have, so that is probably benign. But 2228 seems to be
"There are too many names in the user accounts database."
Exactly what that means, I have no clue, but it could be a Windows problem.
Erland Sommarskog, SQL Server MVP, [email protected]

SQL 2008 R2 SP3 ugrade failure

SQL 2008 R2 SP3 upgrade failure Current Version: Microsoft SQL Server 2008 R2 (SP2) - 10.50.4305.0 (X64) Apr 3 2014 17:55:58 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <x64>(Build 7601: Service Pack 1) (Hypervisor)
Exit code : 325526488 Exit acility code: 871 Exit error code: 9176
Could not find any resources for the specified culture or the neutral culture. Make sure "Errors.resources" was correctly embedded or linked into assembly "Microsoft.SqlServer.Discovery" at compile time, or that all the satellite assemblies
required are loadable and fully signed.
</x64> Please advise.

Hello,
SQL Server setup is trying to find the SQLSysClrTypes_Cpu64 MSI package on the C:\Windows\Installer\257f1f.msi path. I
found the following line on the file you submitted:
Package SQLSysClrTypes_Cpu64: - The path of cached MSI package is: C:\Windows\Installer\257f1f.msi
Try copying the MSI from a SQL Server 2008 R2 RTM media and name it 257f1f.msi or use the FindSQLInstalls.vbs script on the following article to copy the file for you. Put the SQL Server 2008 R2 RTM media on the same place where it was when you installed the
instance before running the script.
http://support.microsoft.com/kb/969052
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2008 to 2014

Similar Messages

Maybe you are looking for