Identificare la versione di SQL server? Semplice!

Cari lettori ben ritrovati dopo questa pausa di una settimana!

Eccoci nuovamente qua assieme, e con le batterie ricaricate al 100%, pronti per nuovi ed interessanti articoli.

Scaldiamo quindi i motori con un articolo easy.

Gli inglesi avrebbero scritto "How to identify your SQL Server version?", noi però siamo italiani e quindi scriviamo come identificare la versione di SQL server installata.

Innanzitutto diciamo che due sono i modi in cui è possibile farlo.

Tramite l' SSMS ovvero il SQL Server Management Studio e tramite comando T-SQL.

Vediamo il primo metodo.

Eseguiamo l' SSMS e dal nome del server facciamo tasto destro sulla voce Proprietà:



 

 

 

 

 

 

 



Si aprirà una finestra.

Da qui possiamo leggere la riga Versione:




 

Per vedere il secondo metodo aprite una nuova console e scrivete:


SELECT @@VERSION

Eseguitela ed ecco qui il risultato.

Possiamo vedere che con questo metodo le informazioni ritornate sono più complete.

Viene infatti ritornato anche il nome della versione e la versione del sistema operativo. 

Microsoft SQL Server 2019 (CTP3.1) - 15.0.1700.37 (X64)   Jun 19 2019 12:44:55   Copyright (C) 2019 Microsoft Corporation  Enterprise Evaluation Edition (64-bit) on Windows 10 Home 10.0  (Build 17134: )

In questo caso la versione 15.0.1700.37 è la versione CTP3.1 di SQL Server 2019.

Facciamo ora un breve riassunto delle versioni di SQL Server in base ai primi due caratteri della versione:

  • SQL Server 2008/ SQL Server 2008R2 = 10
  • SQL Server 2012 = 11
  • SQL Server 2014 = 12
  • SQL Server 2016 = 13
  • SQL Server 2017 = 14
  • SQL Server 2019 = 15


Ricordo poi che è sempre importante aggiornare la versione installata di SQL Server all'ultimo Service Pack / Cumulative update.

Per oggi vi saluto e vi ringrazio delle 1000! visite ricevute in questo mese su questo blog.

A prestissimo ...al prossimo post!


Luca Biondi @ SQLServerPerformance blog!






Next post: Babbo Natale e gli indici univoci filtrati

Previous post:COLLATE e SARGABLE

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more