I am trying to configure log shipping in SQL server but I cannot see the bottom page of Transaction Log Backup Settings.
anyone know why?
I use this version of SQL Server:
Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) Aug 22 2017 17:04:49 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2012 R2 Datacenter 6.3 (Build 9600: ) (Hypervisor)
You should change to an upper screen resolution to view all configuration page of Log Shipping (and another pages, like e.g. Backup/Restore Tasks Config).
Check this link for this topic at Technet Forum.
Related
Our current Azure build agents are using a windows-2019 VM-image and that includes VS2019 and SQL LocalDb 2016.
We're wanting to use a more recent version of SQL LocalDb and I'm trying to find out which version of SQL Localdb ships with VS 2022.
Nothing is mentioned in the Azure hosted agents page or related included software link for windows-latest/windows-2022.
SELECT ##Version from a windows-latest image returns:
Microsoft SQL Server 2019 (RTM-CU12) (KB5004524) - 15.0.4153.1 (X64)
Jul 19 2021 15:37:34
Copyright (C) 2019 Microsoft Corporation
Express Edition (64-bit) on Windows Server 2022 Datacenter 10.0 (Build 20348: ) (Hypervisor)
I have an SSIS project in VS:
Microsoft Visual Studio Professional 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01590
SQL Server Data Tools 14.0.61116.0
Microsoft SQL Server Data Tools
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 13.0.1601.5
Project > Properties > Configuration Properties > Deployment Target Version > TargetServerVersion = SQL Server 2016
I deployed and validated successfully on two SQL server instances, but cannot on a third.
The chief difference I see in the three instances is this:
First (success)
Microsoft SQL Server 2016 (RTM-GDR) (KB4019088) - 13.0.1742.0 (X64)
Jul 5 2017 23:41:17
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows Server 2012 R2 Datacenter 6.3 (Build 9600: ) (Hypervisor)
Second (success)
Microsoft SQL Server 2016 (RTM-GDR) (KB4019088) - 13.0.1742.0 (X64) Jul 5 2017 23:41:17 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows Server 2012 Datacenter 6.2 (Build 9200: ) (Hypervisor)
Third (failed)
Microsoft SQL Server 2016 (SP1-CU5) (KB4040714) - 13.0.4451.0 (X64) Sep 5 2017 16:12:34 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Datacenter 6.3 (Build 9600: ) (Hypervisor)
I have been unable to track down fixes for the errors via Google, and they seem to be the same as when I target SQL Server 2014. I can post those as an edit if necessary, but my suspicion is the Sql Server installation (perhaps an issue specific to the Enterprise edition or something otherwise missing from that install) and not my package based on the above.
Here are the first and likely most relevant errors:
I found that this error goes away if you deploy from within Visual Studio instead of the wizard that is output by the build. However, I don't think you can connect to remote SQL Server instances when deploying from Visual Studio (I think that a Windows login is required).
So the solution was to install SSDT (Visual Studio 2015) on the production machine and deploy locally. This is obviously not great because you then have to move the SSDT project to the target machine every time you want to deploy (i use Git for this).
I'm sure Microsoft will come up with a fix for this eventually... Although at the moment I'm still waiting for them to release SSDT for Visual Studio 2017.
=== EDIT October 2017
SSDT is now available in Visual Studio 2017. However, I found that I still had to deploy from a locally running Visual Studio (but I can't remember why since having tried this a couple months ago from VS2017)
I just installed SQL 2016 Standard Edition because I wanted to use the 'Always Encrypted' feature.
However, when I tried to created a Column Master Key under Security->Always Encrypted Keys->Column Master Key, I got the following error:
productversion: 13.0.160.5, productlevel:RTM, edition:Standard Edition 64bit
Any ideas? Thanks!
I was having the same issue. I fixed it by updating to Sql Server 2016 SP1 from Sql Server 2016.
Previously ##version was:
Microsoft SQL Server 2016 (RTM-GDR) (KB3194716) - 13.0.1722.0 (X64) Sep 26 2016 13:17:23 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows 10 Pro 6.3 (Build 14393: )
Now ##version is:
Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) Oct 28 2016 18:17:30 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows 10 Pro 6.3 (Build 14393: )
Note also that my SSMS is totally up to date.
Tools > Check for Updates > Details - 13.0.16100.1
A coworker has a slightly older build of SSMS and does not even see the option to encrypt columns.
The issue was probably caused by restoring a SQL2014 database. I backed up a 2014 database and then restored it in 2016. SQL may have seen it as a 2014 schema and therefore complained Column Master Key not supported.
How I resolved it: In SSMS 2016, generate .sql script for the imported database (in Advanced settings, choose SQL 2016 script)
Install a new SQL 2016 instance (which may not be necessary will test) and run the .sql generated, rather than the restore option
"Always Encrypted is available in SQL Server 2016 (13.x) and SQL Database. (Prior to SQL Server 2016 (13.x) SP1, Always Encrypted was limited to the Enterprise Edition.)"
Source: https://learn.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-2017
The SQL Server version I'm running is 2012 (11.0.3153) in our dev environment..
I've just applied SQL Server SP2 to my database but the version appears unchanged. I need the version level at 11.0.5058 to match our production.
There was no errors during the installation.
Any idea what's going on?
Select ##version shows:
Microsoft SQL Server 2012 (SP1) - 11.0.3153.0 (Intel X86)
Jul 22 2014 15:41:01
Copyright (c) Microsoft Corporation
Standard Edition on Windows NT 6.2 (Build 9200: ) (WOW64) (Hypervisor)
However I tried applying the patch again and I get this:
Upgrade Status: Installed.
There's not supposed to be a need for a restart but I'm doing that anyway.
Restart did not work either.
I have to copy a db from a remote server to my local dev machine.
What is the best way to do it.
Last night I made a script for the remote db using xSQL Object and ran it on the local server. the script gave a bunch of errors. Below is the select ##version output for the 2 servers. is there a reason the script is not working
The remote server is using SQL server authentication, the local one is using windows authentication
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64)
Jul 9 2008 14:17:44
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 2)
It would be helpful if your provided some of the errors your script produced.
I notice you're using Enterprise and Express editions - these two editions have differing features, described here: http://www.microsoft.com/sqlserver/2008/en/us/editions.aspx. Perhaps you're using a feature that Express edition doesn't support, or your database is too big.
Not sure if the functionality is exactly the same in 2008, but in 2005, you can open up SQL Management Studio, right-click on the dbase you'd like to copy, and then click on Export Data.
This will guide you through a wizard, allowing you to export the data to another SQL dbase, including one that runs on your local machine. Used it many times - works great.
Why don't you just do a backup and restore?