This is a post on installing SQL Server via command; I have a Windows Server 2016 Core running on a local Hyper-V test environment, and I’m installing SQL Server 2019, then uninstalling it.
Windows Server Core is the CLI only version of the Windows OS. This post is a run-through of configuring a new Windows Server 2016 Core host, detailed in the following steps;
A run-through of joining a Windows Server onto a test domain which created in my previous post. There’s 2 parts to this one;# Creating a New Domain User Account.# Joining a Windows Server to a Domain.
This is a run-through on installing Active Directory within a Hyper-V test environment. There’s 5 parts to this one: # Create a Hyper-V Private Network.# Configure Windows TCP/IP Settings.# Rename the Windows Server Host.# Install Active Directory.# Promote the Server to a Domain Controller.
This is a simple guide on installing Windows Server 2016 with Hyper-V. There are two parts to this one.. # Create a new Hyper-V Virtual Machine.# Install Windows Server 2016.
This is a guide on how to exclude a blog category from a blog page in WordPress. I hide my Web Blog posts from the Tech Blog area, so this is a useful one to note down.
When a database file gets full and it needs more space, a growth event will happen. The size of said database growth can be set within the database options, or can be done using the ALTER DATABASE statement as shown below.
Setting maximum database file sizes in SQL Server is something you’d ideally not have to set, but it’s a good last resort option available if you need it.
The Update-Help cmdlet in PowerShell will download the latest help files for PowerShell modules installed on your machine. Running PowerShell as Administrator is a requirement for this one, else you’ll get the following error.
It’s a solid best practise to have TempDB files stored in separate drive, away from your C: drive. This is because TempDB can grow very large, very quickly (within minutes);
The Import Flat File wizard within SSMS was introduced in December 2017 (14.0.17213.0). This is a streamlined version of the Import Data feature and it minimises the user intervention during a file import.
If you’ve lost a database log file and you’re in critical need of the data, well… that would never happen ( ͡° ͜ʖ ͡°) Nevertheless, this is might be a handy random fact to know, that you can attach a data (.mdf) file without the associated log (.ldf) file in SQL Server.