Learning DNS & DHCP (Windows Server 2019) and would like to know the recommended books for learning both of these topics. I searched on Amazon.in and found Windows Server 2019 books but want to know books covering topics like DNS & DHCP
I have to update 50+ servers to use encrypted connection strings. Is there a way to script setting Force Encryption and TrustServerCertificate (e.g Powershell, or ???) so that I don’t have to open Configuration Manager and set on each box?
We have SQL Server 2016 Web Edition on production currently. Since this edition supports replication as Subscriber only, I set up a new server with SQL Server 2019 Standard edition. I want to configure SQL Server 2019 as Publisher and SQL Server 2016 as subscriber. To initialize data for Publisher database on SQL server 2019, I created a backup on SQL Server 2016 and restored it on SQL Server 2019. Since our database is very large, I tried to initialize replication from a backup. So I did reverse backup-restore again by creating a backup of Publisher on SQL Server 2019 and restoring it on Subscriber on SQL Server 2016. But this did not work because [SQL Server 2019 backups cannot be restored by any earlier version of SQL Server] (https://docs.microsoft.com/en-us/sql/relational-databases/databases/copy-databases-with-backup-and-restore?view=sql-server-ver15). Could you please tell me what is the best method for initializing the replication in this case? Thank you very much for reading my question!
I’m trying to add a CmdExec as task in a job, on MS-SQL 2019 on Centos8. However, the task always fails with "running the requested program is not allowed". I have tried specifying both
true as the program, but these also fail.
Is there a list of authorised programs for CmdExec, and is this is editable? I found that MS-SQL Linux 2017 doesn’t support CmdExec, but I think this has been fixed in 2019
The lighting is different between Unity 5.5.2f1 and Unity 2019. Please see the attached image.
I dislike the way the lighting is done in the 2019 version. Both verions are installed out of the box, without any additions.
What do I need to change / set up inside Unity 2019, in order to have the exact lighting as in 5.5.2f1 version?
Does activating the TF9567 seeding mode trace flag speed up the synchronization process in AlwaysOn?
I am using SQL Server 2019.
Here is the scenario. I have a local SQL Server to which I have restored the live SQL Server databases. In order to be GDPR/CCPA compliant, I must anonymize the PII in the local server’s databases. I have a script to do this, and it has been working quite well when the local server is 2008 R2 or 2017. But I just installed 2019 and the same script puts the same value in every row of the table, rather than a different value for each row. It is as though the function is executed only once, then that value is used in the
UPDATE statement. Perhaps it is some kind of optimization 2019 is doing? Here is a snippet of the script.
UPDATE Guest SET GuestFirstName=Utility.dbo.RANDWORD() WHERE GuestFirstName IS NOT NULL;
RANDWORD grabs a random word from a table containing approximately 100,000 English words.
In new futures of Microsoft company remove debugger in
SSMS database engine 15.0 and they are called improvement. (-_-)
I tried use debugger in visual studio 2019 by this answer :
How to add the Debug button to SSMS v18?
But i’ve below error when run debugging :
We just upgraded from SQL Server 2008 R2 to SQL Server 2019(Compability lvl 150).
We have two different stored procedures that started failing after the upgrade, with error messages like this:
Msg 8632, Level 17, State 2, Procedure BuildSelfSaleStats, Line 14 [Batch Start Line 4] Internal error: An expression services limit has been reached. Please look for potentially complex expressions in your query, and try to simplify them.
Whats really strange is that this particular stored procedure doesnt take any arguments, and when we simply execute the body of the SQL code in SSMS, it works fine(!?).
What might cause some SQL code that works fine when executed in SSMS, to suddenly start failing when its wrapped in a stored procedure?