Skip to content

Instantly share code, notes, and snippets.

"""
This script is used to manage AWS CloudFormation stacks.
It allows the user to:
- Set the AWS region
- Check the account ID
- List all the stacks that start with "AWSAccelerator" and have StackStatus either "UPDATE_COMPLETE" or "CREATE_COMPLETE"
- Sort these stacks according to their CreationTime
- Remove termination protection from these stacks.
- Delete these stacks one by one
"""
@fortran01
fortran01 / fetch_ts.py
Last active January 8, 2024 19:07
Fetch machine-stats time-series data from the Tidal platform
import json
import os
import pandas as pd
testing_flag = False # Set to True to only fetch data for the first two servers with machine stats
def list_servers_without_machine_info(df_servers):
df_servers_without_machine_info = df_servers[
df_servers['ram_allocated_gb'].isna()
| df_servers['storage_allocated_gb'].isna()
- name: Workload1-VPC
account: Workload1
region: us-east-1
cidrs:
- 172.31.0.0/16
internetGateway: true
enableDnsHostnames: true
enableDnsSupport: true
instanceTenancy: default
routeTables:
# Install in Centos 7:
# https://www.server-world.info/en/note?os=CentOS_7&p=oracle19c&f=6
# It is possible to modify the 'sys' and 'system' user passwords
[oracle@host ~]$ sqlplus "/ as sysdba"
# SQL> alter user sys identified by syspw;
# SQL> alter user system identified by systempw;
# Test connecting to the default SID using an Oracle DB Client
# Connect to SID=ORCLCDB as sys using the SYSDBA role
# # Check if running as an administrator
# $currentUser = New-Object Security.Principal.WindowsPrincipal $([Security.Principal.WindowsIdentity]::GetCurrent())
# $adminRole = [Security.Principal.WindowsBuiltInRole]::Administrator
# if (-not ($currentUser.IsInRole($adminRole))) {
# Write-Error "You must run this script as an administrator because we need to set the trusted hosts list for WinRM."
# exit 1
# }
# # Prompt for the Tidal workspace URL (e.g., https://workspace.tidal.cloud)
# $url = Read-Host -Prompt "Enter Tidal workspace URL (e.g., https://workspace.tidal.cloud)"
@fortran01
fortran01 / automate_machinestats_nondomain.ps1
Last active October 20, 2023 18:43
automate_machinestats_nondomain.ps1
# cd to C:\machine_stats\windows
Set-Location C:\machine_stats\windows
# Prompt for the username of the service account to use to connect to the target hosts
$Username = Read-Host "Enter the username of the service account to use to connect to the target hosts"
# Create the machine-stats wrapper script C:\machine_stats\windows\run_default.ps1 to run runner.ps1
$Content = "C:\machine_stats\windows\runner.ps1 ```
-UserName $Username ```
-ServersPath `"C:\machine_stats\windows\servers.txt`" ```
Server Name Server Version Feature Parity Category Impacted Object Impacted Object Details Issue Recommendation Additional Reading
172.31.25.101 SQL Server 2017 UnsupportedFeature pubs SQL Server Service Broker provides native support for messaging and queuing applications in the SQL Server Database Engine. Service Broker feature is not supported in Azure SQL Database. Service Broker feature is not supported in Azure SQL Database. Consider migrating to Azure SQL Managed Instance that supports service broker within the same instance. Alternatively, migrate to SQL Server on Azure Virtual Machine. ()
We can make this file beautiful and searchable if this error is corrected: Unclosed quoted field in line 3.
"Server Name","Server Version","Database Name","Issue","Source Compatibility Level","Impact","Target Compatibility Level","Compatibility Category","Recommendation","More Info","Impacted Object Type","Impacted Object","Impacted Object Details"
"172.31.25.101","SQL Server 2017","pubs","Service Broker feature is not supported in Azure SQL Database","140","SQL Server Service Broker provides native support for messaging and queuing applications in the SQL Server Database Engine. Service Broker feature is not supported in Azure SQL Database.","140","BreakingChange","Service Broker feature is not supported in Azure SQL Database. Consider migrating to Azure SQL Managed Instance that supports service broker within the same instance. Alternatively, migrate to SQL Server on Azure Virtual Machine.","()","Database","pubs",""
"172.31.25.101","SQL Server 2017","pubs","Service Broker feature is not supported in Azure SQL Database","140","SQL Server Service Broker provides native support for messaging and queuing applications
Server Name Server Version Status Description
172.31.25.101 SQL Server 2017 Success Assessment was successfully completed: 0 issues and 1 recommendations
Server Name Server Version Database Name Status Description
172.31.25.101 SQL Server 2017 nwnd Success Assessment was successfully completed: 0 issues and 0 recommendations
172.31.25.101 SQL Server 2017 pubs Success Assessment was successfully completed: 3 issues and 0 recommendations