I created a new instance of SQL elastic pool server, the displayed version of sql server is 12.0.2000.8. Is it possible to upgrade it to 13.x ?
Azure SQL Databases always run on latest stable version of the SQL Server database engine.(Refer to link for more details).
You can run below queries to check the same after creating the database:
select ##version as version;
select serverproperty('ProductVersion') as [version],serverproperty('Edition') as [edition];
SELECT name, compatibility_level FROM sys.databases;
You can find the version using the SQL query but that will always show you v12.x.x.x.
Hope this will help.
Thanks
Related
I specified following catalog for SQL Server
connector.name=sqlserver
connection-url=jdbc:sqlserver://192.168.1.1
connection-user=build_agent
connection-password=build_agent
When I try running queries against it, it seems that I can access master database only. How can I specify specific database?
From Trino (formerly Presto SQL) SQL Server connector documentation (https://trino.io/docs/current/connector/sqlserver.html):
connection-url=jdbc:sqlserver://<host>:<port>;database=<database>
I believed that I always got the latest version of SQL Server when creating a new Azure database from the Azure Portal. But that is not happening.
I always get sql Server version (12.0.2000.8) which is SQL 2014. I can't find other places to set a new compability level either.
Is there a problem with my subscription (pay as you go)??
Have any of you had the same experience as me, have you been able to solve it?
The reason I want SQL 2017 is that I want to publish SSIS packages to the SSISDB catalog, which is not possible on SQL 2014?
Hope any of you can help me out here
regards GEir
It's possible to use SSIS on DB engine 12 on Azure. Check out official documentation.
Additionally, you may upgrade your already-created azure databases by setting COMPATIBILITY_LEVEL modificator. Look into ALTER_TABLE documentation for examples.
Please note that although SQL Azure's engine share similar "engine api" as SQL Server 2014 (v12), those are not the same. What's more relevant in terms of supported features is maximum supported "Compatibility level".
I have installed SSMS2017, i don't see Query Store page under db level properties.
I also tried through command line query:
alter database <db_name> SET QUERY_STORE = ON;
this doesn't seem to be working either.
Could someone please help on how can i enable query store ?
Thanks.
Upgrading SSMS alone won't work, you need both SQL Server 2016+ as well as latest SSMS to support viewing Query Store Options.
-- Major Build Version is 13 for SQL 2016 and 14 for SQL 2017
SELECT ##VERSION
We have a sql2k8 database that uses sp_xml_preparedocument, a master db system extended stored procedure, that needs to go to Azure. The migration tools (SSMS2016 wizard) give a validation error: SQL71501 that [dbo].[sp_xml_preparedocument] is a missing reference, when validating the export.
I can't see any way to reference the sp so it can be migrated. Intellisense always shows an error too.
Could you first verify that your code works fine on Azure SQL when you manually execute the scripts? When I execute queries with sp_xml_preparedocument from MSDN on my Azure SQL Database it works fine.
If your code works, then it is a problem in SSMS migration assistant, so in that case you should report bug on SQL Server Connect site, with some minimized repro script, so SQL Server team can fix it.
Use SQL Server 2016 Enterprise with Service Pack 1 (x64) . The SP1 should support Azure DB . The 2012 version of Sql server might do iT.
I created a database in SQL Server 2008. I detached the database and I copied the .mdf over to the server, which is running SQL Server Enterprise Manager (SQL Server 2000).
When I try to attach the MDF I get...
Microsoft SQL-DMO (ODBC SQL State: HY000) Error 602: Could not find
row in sysindexes for database ID 13, object ID 1, index ID 1. Run
DBCC CHECKTABLE on sysindexes.
What does this mean? Is this because the db was created in a newer version?
From the documentation on the (I believe depreciated, but used in SQL Server 2000) sp_attach_db stored proc:
A database created by a more recent version of SQL Server cannot be
attached in earlier versions.
I think you'll have to script the schema and data of your database.
Pinal Dave has a good tutorial on how to do this here - just remember to make sure you choose the following settings:
Under General:
Script for server version: SQL Server 2000
Under Table/View options:
Script data: True
Remember to double check the settings for any others you might be interested in, such as foreign keys, triggers etc.
This is do-able, but you'd need to convert it to the SQL 2000 format before detaching it and attaching it on the old server. Here are the steps:
In entreprise manager, right click the database
Choose properties
On the left, click Options
Change the "Compatibility Level" to SQL Server 2000 (80)
Then save, and detach before reattaching on the old server.