Finally! T-SQL Reference for SQL 2014 available for download!

With a mere delay of four month since the release, it is now possible to download the T-SQL Reference for SQL 2014 for your local copy of Books Online. Due to some reorganisations of the reference material on MSDN, the language reference was misisng from
the initial download.
To get the reference, you need to use Manage Help Settings, which you find the SQL 2014 program group. Select the option "Install content from online". Once all information has been loaded, scroll down to the SQL Server 2014 group and you will
SQL Server Language Reference with an Add option, which you should select.
Now, SQL 2014 uses Help Viewer 1.0, which is very poor, and versions 2.0 and 2.1 which ships with VS 2012/2013 is much more pleasant to use. Thanks to SQL Server MVP Simon Sabin, you can get the SQL 2014 into Help Viewer 2.x in this way. Go to
https://helpviewerredirector.codeplex.com/
save the file to a directory. Open a command prompt in that directory and run "HelpViewerRedirector download". Then in Help View, go to manage settings, and select install content from disk. Browse to the folder and select the files you want to see
in Help Viewer 2.1.
Erland Sommarskog, SQL Server MVP, [email protected]

To get the reference, you need to use Manage Help Settings, which you find the SQL 2014 program group. Select the option "Install content from online". Once all information has been loaded, scroll down to the SQL Server 2014 group and you will
SQL Server Language Reference with an Add option, which you should select.
If you need more detailed instructions on this part, see the comment from Microsoft added today (2014-08-01) to
http://connect.microsoft.com/SQLServer/feedback/details/859047/t-sql-reference-and-xquery-reference-missing-from-downloadable-version-of-bol-2014
Erland Sommarskog, SQL Server MVP, [email protected]

Similar Messages

SQL 2014 Linked Servers with Availability Groups

Good afternoon All. Hope your well. We have SQL 2014 Availability group setup over multiple Subnets.
So basically Instance A(In Primary DC), and Instance B (Secondary Replica, in secondary DC), with AG1 (Availability Group)
When I connect to the instance Directly (using SQL management Studio), and attempt to create a linked Server to another SQL 2014 instance (Instance D, Both use the same Service Account), I am able to successfully connect, and run query on the Linked Server.
However when I connect to the Availability group, I attempt to open the linked server (to Instance D) and receive the following error:
Login Failed for User 'NT Authority\Anonymous Logon'
This above only happens when I connect to the AG1, and not the instances directly. I have given the Service account permissions to Read and Write its own SPNs (Using ADSI Edit). Researching this people have stated to add the Availability Group Name as an
SPN to the Service account;
Setspn -A MSSQLSVC\AG1.mydomain:1433 mydomain\ServiceAccount
However, Im a little unsure at this stage, should the port in the above command reflect what the AG1 endpoint ports are? As I have done that (as well as trying port 1433), and unfortunately the error still happens. Your assistance would be appreciated,
kind regards,

Hi Nsaneone,
>> Setspn -A MSSQLSVC\AG1.mydomain:1433 mydomain\ServiceAccount
>>However, Im a little unsure at this stage, should the port in the above command reflect what the AG1 endpoint ports are?
The port in the above command should reflect the port which the availability group listener is listening on, but not the endpoint port.
>> Login Failed for User 'NT Authority\Anonymous Logon'
According to the error message, it always occurs when the Kerberos authentication fails in SQL Server, there are proposals for you troubleshooting the issue.
1. Make sure that your service accounts have “Trust this user for delegation to any service (Kerberos only)” enabled in Active Directory.
2. Make sure that SPN’s are registered successfully for all SQL Server instances.
3. The server must be using TCP/IP or named pipes network connectivity.
For more details about the error, please review the following links.
http://mssqlwiki.com/tag/login-failed-for-user-nt-authority-anonymous/
http://blogs.msdn.com/b/karthick_pk/archive/2009/01/23/kerberos-authentication-in-sqlserver.aspx
Thanks,
Lydia Zhang

SQL 2014 Always On Availability Groups

It appears to be working. I've attached a picture of the role that was created when I was finished configuring WSFC. Is there something that would I can check that would give me a definitive answer?

I am testing SQL 2014 availability groups and I have run into a snag. I setup a win2k8 r2 DC and two windows 2012 R2 servers running SQL 2014 standard. I setup failover clustering for the two SQL servers. In SQL Management Studios I have setup the availability group and everything seems to have been successful. except when the wizard completes I get an error Creating availability group listener resulted in an error.....Error 41009.The AG seems to be working I can connect to the AG in SSMS using the listener name. But in the Availability Group Listener section there is no listener setup. Also the databases also seem to be read only if I connect thru the listener name. The AD computer account seems to be setup correctly. I am just unable to create the listener in SQL. Is there a security permission in SQL that I could have missed. Any...
This topic first appeared in the Spiceworks Community

SQL 2014 - Cumulative Update 2 and/or 3 break Master Data Services

Hi,
Strange issue, but I'll try to lay it out as clearly as possible.
If we apply CU #2 or #3 on a licensed SQL 2014 Entr. installation, we can't get MDS working. We receive the "The current SQL Server edition is not supported by MDS" error.
If we do the same, but use the downloaded trial isntaller from the Microsoft site as base for our installation, everything works fine.
If we again use that trial install software, but instead of choosing trial, we enter our product key from above, again MDS results in the beforementioned error.
So to wrap up:
Install SQL 2014 with licensed software + CU #2 or #3 --> MSD won't work (The current SQL Server edition is not supported by MDS)
Install SQL 2014 with a downloaded trial installer + apply CU#2 or #3 --> MDS works
Install SQL 2014 with a downloaded trial installer, BUT enter our Product Key + apply CU#2 or #3 --> MSD won't work (The current SQL Server edition is not supported by MDS)
Why do we need CU #3? Our MDS database will reside on another server with a named instance. Apparently #CU 3 is needed if we want this setup to work.
But what startles me the most is the fact that I have no problem at all when installing SQL 2014 as a trial, but everything breaks if I install SQL 2014 with a Product Key.
Regards
Tony

Hello,
Could please file a bug report on the Microsoft Connect Web site? If possible, please share the link with us.
https://connect.microsoft.com/sqlServer/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Best practice configuration for SQL 2014 to achieve HA when hosted on Hyper-V 2012R2 cluster

Hi,
I've had a hunt around but so far I've not found a conclusive answer to my question. I am currently moving from a SQL 2008R2 (physical tin) failover cluster to a virtual environment build on Hyper-V 2012R2. I am building everything with SQL 2014
SP1.
I want to achieve the same level of high availability that I currently have and at the same time make sure that I can replicate (DR) data offsite (Azure) in the future. I have two options with SQL which are clustered instance (basically the same as
I have now) or AlwaysOn Availability Groups for database level HA.
I am unsure which is the best method to use when the SQL nodes are highly available guests on Hyper-V, trying to imagine how the guests will all move around in the case of a host server failure is a bit mind boggling to say the least.
I am leaning towards a instance failover but I would appreciate any input/advice etc.
Thanks
Rob

Hi Rob,
To start with I will not be installing SQL Server 2014 with SP1, as SP1 has bugs and Microsoft has disabled its download. See reference: http://www.eweek.com/database/microsoft-halts-sql-server-2014-sp1-downloads.html
With regards, I would go for AlwaysOn Availability Groups configuration, because it has several benefits:
You will get same amount of high availability you normally get with native cluster configuration, if you use AlwaysOn configuration. However, AlwaysOn configuration provides more granular high availability, and fail-over are invisible to the application,
if you using Availability Group listener to connect to server.
You can offload read-only workloads to secondary replica.
You can perform transaction log backups on secondary replica.
Reduce production downtime during patching or other planned work on the server.
So in short, you should use AlwaysOn configuration.
Regards,
Basit A. Farooq (MSC Computing, MCITP SQL Server 2005 & 2008, MCDBA SQL Server 2000)
http://basitaalishan.com
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Restore Log with Standby Mode on VHDX disk problem - hotfix for SQL 2014 needed

Restore Log with Standby Mode on Virtual VHDX disk cause a 9004 error in SQL Server 2014 ( test performed on Web edition and Standard version )
Similar Bug for SQL 2008R2 is already registered with number hotfix
KB2987585
Restore operations always fail in Hyper-V R2 Server in situations ( text copied from
KB2987585 page )
The primary database has its transaction log file (.ldf) stored on a disk that has "Bytes per Physical Sector" set as 512 bytes.
You take the transaction log backups of this database, and then you try to restore it by using the standby option on the secondary database.
The secondary database transaction log file (.ldf) is located on a VHDX disk that has "Bytes per Physical Sector" set as 4,096 bytes.
In this scenario, the restore operation fails and returns the following error message:
Error: 9004, Severity: 16, State: 6.
An error occurred while processing the log for database '<databasename>'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
After this error occurs, the secondary database goes into a suspect state.
So restore from Generation1 to Generation2 machine ( where only VHDX disk is possible ) always fails and database is not accessible.
Please create hotfix for SQL 2014 version

Please create hotfix for SQL 2014 version
This is a community forum, no one of use can create a hotfix for SQL Server.
Raise a case at Microsoft Support or create an entry at MS Connect:
http://connect.microsoft.com/SQLServer
Olaf Helper
[ Blog] [ Xing] [ MVP]

(BUG??) Team Foundation Server 2013 Update 4 Support for SQL 2014

Scenario: On Windows 2012 R2 x64 I have installed SQL, Reporting Services & AS 2014 (applied all updates through Windows Update), SharePoint 2013 Foundation, and installed Team Foundation Server 2013 RTM (did not configure).
Before configuring TFS, I applied Update 4 to the server (not update 1,2 or 3 directly). When trying to configure I get the following error:
==========================
TF255146: Team Foundation Server requires SQL Server 2012 SP1 (11.00.3000) or greater. The SQL Server instance you supplied is version 12.0.2254.0.
TF400403: The Report Server instance specified is version 12.0.2254.0, the minimum supported version is 11.0.3000.
TF400070: A required version of a component is not installed on the application tier. You must exit the Team Foundation Administration Console and install a supported version of either SQL Server Analysis Services of the SQL Server Client Tools on the application
tier to ensure that the Analysis Services object model is present for warehouse processing.
====================================
My understanding is that as of Update 2 (or was it 3) that SQL 2014 was supported. However it appears if that particular update is not installed directly it bypasses the check. Can someone verify I am seeing the intended result or is this a bug?

Hi Jazzy,
Thanks for your post.
And thank you for sharing your experience here. It will be very beneficial for other community members having the similar questions.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SQL 2014 cluster installation on mounting point disks error: Updating permission setting for file

Dear all,
I am attempting to install SQL 2014 fail over cluster under a physical windows 2012 R2 server which have mounting point disks.
At the finish of setup I get the following error message.
Could you please help me on this?
Thanks
The following error has occurred:
Updating permission setting for file 'E:\Sysdata!System Volume Information\.....................................' failed. The file permission setting were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: go.microsoft.com/fwlink
I am using an administrator account which have all security rights (cheched on secpol.msc mmc) needed for installation.

Hi Marco_Ben_IT,
Do not install SQL Server to the root directory of a mount point, setup fails when the root of a mounted volume is chosen for the data file directory, we must always specify
a subdirectory for all files. This has to do with how permissions are granted. If you must put files in the root of the mount point you must manually manage the ACLs/permissions. We need to create a subfolder under the root of the mount point, and install
there.
More related information:
Using Mount Points with SQL Server
http://blogs.msdn.com/b/cindygross/archive/2011/07/05/using-mount-points-with-sql-server.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

SQL 2014 - Group Membership for sysadmin permissions not working

I am using SQL 2014 on Windows Server 2012 R2 and am running into a permission issue. During the install I specified the local server's Administrators group as well as my specific domain account to have sysadmin privileges.
The issue is that accounts that are a member of the local server's administrators group can't even login to SQL Server Management Studio unless they are specifically granted permissions for their account (my domain account works fine as it has a specific
credential in SQL).
The log just gives the following error:
Login failed for user 'domainname\username'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
Error: 18456, Severity: 14, State: 11.
I haven't had this issue in previous versions. Is there something that must be done differently in 2014 to grant permissions to groups?

Hi, something like
this?
Bye
Questo post è fornito "così com'è". Non conferisce garanzie o diritti di alcun tipo. Ricorda di usare la funzione "segna come risposta" per i post che ti hanno aiutato a risolvere il problema e "deseleziona come risposta"
quando le risposte segnate non sono effettivamente utili. Questo è particolarmente utile per altri utenti che leggono il thread, alla ricerca di soluzioni a problemi similari. ENG: This posting is provided "AS IS" with no warranties, and confers
no rights. Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Gathering physical memory for SQL 2005..SQL 2014

Hi All,
I'm trying to write a query to gather physical memory across my SQL servers (from SQL 2005 to SQL 2012).
However, the sys.dm_os_sys_info DMV (the column for physical memory) is not the same after the switch to SQL 2012+.
Here is the original query:
SELECT
@@SERVERNAME AS ServerName,
CASE WHEN LEFT(CAST(serverproperty('productversion') as char), 1) = 9 THEN '2005'
WHEN LEFT(CAST(serverproperty('productversion') as char), 4) = 10.0 THEN '2008'
WHEN LEFT(CAST(serverproperty('productversion') as char), 4) = 10.5 THEN '2008R2'
WHEN LEFT(CAST(serverproperty('productversion') as char), 2) = 11 THEN '2012'
END AS MajorVersion,
SERVERPROPERTY ('productlevel') AS MinorVersion,
SERVERPROPERTY('productversion') AS FullVersion,
SERVERPROPERTY ('edition') AS Edition,
SERVERPROPERTY('collation') as Collation,
cpu_count as CpuCount,
physical_memory_in_bytes/1024/1024 as PhysMemMB
FROM [sys].[dm_os_sys_info]
If I run that on SQL 2014, it fails because 'physical_memory_in_bytes' is now called 'physical_memory_kb'
I tried to do an IF..THEN..ELSE:
IF (cast(serverproperty('productversion') as char) like '11.%')
Then change the query accordingly but it would fail because i guess when it tried to parse the whole code, one of the T-SQL variations would have a column that did not exist in that particular version of SQL Server.
Is there a way I can get physical memory across SQL 2005..SQL 2012 or rewrite the T-SQL above to be able to run on both?
Thanks in advance

Oh it seemed like you are asking SQL Server memory. the name for physical memory column ha changed only in SQL Server 2012. I wrote below script just first run select SERVERPROPERTY('ResourceVersion') to get exact resource database version of
SQL Server 2012 and then replace it in below script
IF cast ( SERVERPROPERTY('ResourceVersion') as char (10) )= '11.00.2000'--2012 resource database version
select (physical_memory_kb/1024)as Physical_mem_MB from sys.dm_os_sys_info
else
select (physical_memory_in_bytes/1024/1024) as physical_mem_MB from sys.dm_os_sys_info
Edit: A more optimized query
If cast (LEFT( CAST(SERVERPROPERTY('ResourceVersion') AS VARCHAR(20)),2) as INT) in ('11','12')
select (physical_memory_KB/1024) as Physical_Mem_MB from sys.dm_os_sys_info
--else it uses for 2005-08R2
else select (physical_memory_in_bytes/1024/1024) as Physical_Mem_MB from sys.dm_os_sys_info
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 Articles
Hi Shanky,
Doesn't work and that's what I meant in my initial post..when I run that code against a SQL 2012 instance, it parses fine but when I execute it I get:
Msg 207, Level 16, State 1, Line 6
Invalid column name 'physical_memory_in_bytes'.

SQL Server Data Tools for SQL 2014 setup

Hello,
I have been using SQL server 2008 with Visual Studio 2008 to perform the ETL processes.
I have recently got SQL 2014 and realized that Business Intelligence Development Studio does not come with it so I have to download SQL Server Data Tools for Visual Basics 2012 or 2013 from:
https://msdn.microsoft.com/en-us/data/hh297027
Can someone advise what exactly I have to do if I want to start using SQL 2014 with SSDT? I still have VB 2008 installed and all my packages were created with that version.
Do I need to download VB 2012 or 2013 plus SSDT and then SSDT? Do I also uninstall VB2008?
Thanks in advnce

Hello,
If you want to keep developing packages for SQL Server 2008 then you need to use BIDS 2008, you cannot use SSDT.
If you want to upgrade BIDS projects to SSDT, then you can use Integration Services Project Conversion Wizard from Visual
Studio or SSIS Package Upgrade Wizard from SQL Server Management Studio (SSMS).
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQLEXPRWT_x64_ENU.exe for SQL 2014 express seems to be incomplete?

Hi,
I have downloaded the executable SQLEXPRWT_x64_ENU.exe for SQL 2014 express several times, but every time I run the executable, when it is almost done extracting I get the error: Extraction failed.
When I run the setup.exe in the directory where the extracted files reside, the installation will eventually fail with the error it is missing files (which sounds logical seen the previous error).
So it occurs to me that the "SQL 2014 Express With Tools" executable (SQLEXPRWT_x64_ENU.exe) found at http://www.microsoft.com/en-us/download/details.aspx?id=42299 is broken.
Anyone with the same issues or have any idea where I can download the correct executable?
By the way the total size of the separate downloads of the management tools and the sql express version is larger than the download with the tools included:
SQLEXPRWT_x64_ENU.exe = 833.2 MB
SQLEXPR_x64_ENU.exe + SQLManagementStudio_x64_ENU.exe = 880.6 MB
For me this confirms my suspicion
Regards,
Erik

Hi,
Based on your description there IS something wrong with the download. Have you actually downloaded it and tried what I am describing, so you can rather base it on experience than just a description?
1. If I need a third party application to successfully extract a self-extracting executable, than to me there is something wrong with the download.
2. the /X makes no sense because I get the same specify location dialogue box if I just run the executable.
Taken all the above into account including the size differences mentioned in my starting post, to me the self extracting executable is still broken/faulty/incomplete.
Hi Erik,
Actually, I have done a test, firstly downloaded the SQLEXPRWT_x64_ENU.exe file from the same website:http://www.microsoft.com/en-us/download/details.aspx?id=42299, and extracted it from the command prompt, and then I installed the SQL 2014 Express on my computer
successfully.
Since your self-extracting executable is still incomplete.I recommend you to check if there is an anti-virus software or other third-party software on your computer blocking the process of downloading, also you can try to download the SQLEXPRWT_x64_ENU.exe
file from a different browser, and check if you can implement the extraction successfully.
In addition,this issue might also be caused by your Internet Service Providers (ISP). In order to enhance the network performance, some ISPs may deploy cache servers, when you download the SQLEXPRWT_x64_ENU.exe file from Microsoft official website, it
will redirect your installation media file to the local cache server, and it might cause the download file to be broken, then you encounter the error when extracting file. I recommend you to contact to your ISP to solve the problem, then download again
and check if it can extract successfully .
Thanks
Lydia Zhang

Does SCCM 2007 R3 support SQL 2014 if not is there any mitigation plan for this

Hi ,
As part of Database migration to SQL 2014, wanted to check whether SCCM 2007 R3 support SQL 2014 or not.
I have a link for SCCM 2012 which tells it does support to SCCM 2012, but in upgrade mode.
Is there any other approch instead of upgrade on SCCM 2012.
Please let us know.
http://windowsitpro.com/configuration-manager/configmgr-2012-supported-sql-server-2014-only-if-you-upgrade
Regards
Sudam Bisi
CTS

I doubt CM07 will support SQL 2014, particularly when mainstream support has ended already.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

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

SQL 2014 Exp Wont Install Win 8.1

Hello All,
Im really struggling to install SQL 2014 express on my windows 8.1 SL pc. x64
i installed SQL 2008 first but when i tried to install the studio management, it refused to work.
so i redownloaded the latest setups. ive tried both 32bit and 64bit
SQLEXPR_x86_ENU.exe 172mb
SQLManagementStudio_x86_ENU.exe 689mb
It just stays on the one screen after the landing page. ive left my pc for 6 to 8 hours...
ive tried this more than once... and no luck...
Note i have cleaned the registry and directorys each time.
Logs------------
http://1drv.ms/1pJFzTq
http://1drv.ms/1pJFAXC

I am little confused are you trying to install SQL server 2008 express or SQL server 2014 express.
You should first refer to
Hardware and Software requirements for installing SQL server 2014
You should also read Installing SQL server On windows 8
Finally when you are ready download
SQL server 2014 express
Edit: reg logs you posted it seems your machine where you are installing SQL server does not have internet connection. Internet connection is required for installation of SQL server 2014 express read Hardware and software requirements.
06) 2014-05-30 03:21:36 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: SQL Server Setup was not able to scan for product updates within 5 minutes. This can happen when there are Internet or network issues. ---> Microsoft.SqlServer.Configuration.SmartSetupExtension.MuSelectServerTimeoutException: SQL Server Setup was not able to scan for product updates within 5 minutes. This can happen when there are Internet or network issues.
Please revert if any Issue.
Hope this helps
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

Finally! T-SQL Reference for SQL 2014 available for download!

Similar Messages

Maybe you are looking for