Windows Task Scheduler "Launch request ignored, instance already running"

'If the task is already running, the following applies" make it "Do start a 
new intstance".

Change this to "Run a new instance in parallel"

mysql match against example

 mysql match against example

SELECT * FROM tbl WHERE match(hotel) against('+the mill hotel' IN BOOLEAN MODE) 

INSERT INTO SELECT Syntax

 

INSERT INTO SELECT Syntax

 

INSERT INTO table2
SELECT * FROM table1
WHERE condition;

Copy only some columns from one table into another table:

INSERT INTO table2 (column1, column2, column3, ...)
SELECT column1, column2, column3, ...
FROM table1
WHERE condition;

 

 https://docs.microsoft.com/en-us/devops/develop/git/migrate-from-tfvc-to-git

Migrate from TFVC to Git

• Article
• 06/14/2021
• 4 minutes to read
• 
  

Azure DevOps provides a simple migration tool to migrate from Team Foundation Version Control to Git.

Before migrating source code from a centralized version control system to Git, understand the differences between the two and prepare for the migration.

Requirements

In order to make migrations simple, there are a number of requirements on the TFVC Import tool:

1. Only a single branch is migrated. When planning the migration, choose a new branching strategy for Git. Migrating only the main branch supports a topic-branch based workflow like GitFlow or GitHub Flow.
2. A tip migration, importing only the latest version of the source code, is suggested. If TFVC history is simple, there is an option to migrate some history, up to 180 days, so that the team can work only out of Git. For more information, see Plan your migration to Git.
3. Binary assets like images, scientific data sets, or game models must be excluded from the repository. These assets should use the Git LFS (Large File Support) extension, which the import tool does not configure.
4. The imported repository cannot exceed 1GB in size.

If the repository does not meet these requirements, use the Git-TFS tool to perform the migration.

In general, the process to migrate from TFVC is very easy:

Steps to migrate

1. Check out the latest version of the branch from TFVC onto the local disk.
2. Remove binaries and build tools from the repository and set up a package management system like NuGet.
3. Convert version control system-specific directives. For example, convert .tfignore files to .gitignore, and convert .tpattributes files to .gitattributes.
4. Check in the final changes to Team Foundation Version Control and perform the migration to Git.

Steps 1-3 are optional. If there are not binaries in the repository and there is no need to set up a .gitignore or a .gitattributes, then skip straight to performing the migration.

Check out the latest version

Create a new TFS workspace and map a working folder for the server directory being migrated to Git. This does not require a full working folder mapping. Only map folders that contain binaries to be removed from the repository and folders that contain version control system-specific configuration files like .tfignore.

Once mappings are set up, get the folder locally:

prettyprint

tf get /version:T /recursive

Remove binaries and build tools

Due to the way Git stores the history of changed files by providing a copy of every file in history to every developer, checking in binary files directly to the repository will cause it to grow quickly and cause performance issues.

For build tools and dependencies like libraries, adopt a packaging solution with versioning support, such as NuGet. Many open source tools and libraries will already be available on the NuGet Gallery, but for proprietary dependencies, create new NuGet packages.

Once dependencies are moved into NuGet, make sure that they will not be included in the Git repository by adding them to .gitignore.

Convert version control-specific configuration

Team Foundation Version Control provides a .tfignore file that will ensure that certain files are not added to the TFVC repository. This can be used for automatically generated files like build output so that it is not accidentally checked in.

If the project relies on this behavior, convert the .tfignore file to a .gitignore file.

Cross-platform TFVC clients also provide support for a .tpattributes file that controls how files are placed on the local disk or checked in to the repository. If a .tpattributes file is in use, convert it to a .gitattributes file.

Check in to TFVC and perform the migration

Check in any changes that remove binaries, migrate to package management, or convert version control-specific configuration. Once this final change is made in TFVC, the import can be performed.

Follow the Import repositories documentation to actually perform the input.

Advanced migrations

The Git-TFS tool is a two-way bridge between Team Foundation Version Control and Git, and can be used to perform a migration. Git-TFS is appropriate to attempt a migration with full history, more than the 180 days that the Import tool supports, or to attempt a migration that includes multiple branches and merge relationships.

Before attempting a migration with Git-TFS, be aware that there are fundamental differences between the way TFVC and Git store history:

• Git stores history as a snapshot of the repository in time, while TFVC records the discrete operations that occurred on a file. Change types in TFVC like rename, undelete and rollback cannot be expressed in Git. Instead of seeing that file A was renamed to file B, it will only track that file A was deleted and file B was added in the same commit.
• Git does not have a direct analog of a TFVC label. Labels can contain any number of files at any specific version and can reflect files at different versions. Although conceptually similar, Git tags point to a snapshot of the whole repository at a point in time. If the project relies on TFVC labels to know what was delivered, Git tags may not provide this information.
• Merges in TFVC occur at the file level, not at the entire repository. Only a subset of changed files may be merged from one branch to another. Remaining changed files may then be merged in a subsequent changeset. In Git, a merge affects the entire repository, and both sets of individual changes cannot be seen as a merge.

Because of these differences, it is recommended that users do a tip migration and keep their TFVC repository online, but read-only, in order to view history.

To attempt an advanced migration with Git-TFS, see cloning a single branch with history or cloning all branches with merge history.

Update the workflow

Moving from a centralized version control system to Git is more than just migrating code. The team needs training to understand how Git is different from the existing version control system and how these differences affect day-to-day work.

Learn more about migrating from centralized version control to Git.

---

Recommended content

• Import repositories from TFVC to Git - Azure Repos

  Search your Git repo in Azure DevOps Services or TFS for a specific file or folderImport your repositories from TFVC to Git repositories within the same account.

• Plan your migration to Git - Azure DevOps

  Switching from centralized version control to Git? Git uses a fundamentally different model for storing code. Here's what you need to know.

• Git and TFVC version control - Azure Repos

  Choosing which version control to use in Azure Repos

• Use TFVC and Git repos in the same project - Azure Repos

  Using Version Control for your project in Azure DevOps

Install Chocolatey

 

Install Chocolatey for Individual Use:

1. First, ensure that you are using an administrative shell - you can also install as a non-admin, check out Non-Administrative Installation.

2. Install with powershell.exe

   📝 NOTE: Please inspect https://community.chocolatey.org/install.ps1 prior to running any of these scripts to ensure safety. We already know it's safe, but you should verify the security and contents of any script from the internet you are not familiar with. All of these scripts download a remote PowerShell script and execute it on your machine. We take security very seriously. Learn more about our security protocols.

   With PowerShell, you must ensure Get-ExecutionPolicy is not Restricted. We suggest using Bypass to bypass the policy to get things installed or AllSigned for quite a bit more security.

   • Run Get-ExecutionPolicy. If it returns Restricted, then run Set-ExecutionPolicy AllSigned or Set-ExecutionPolicy Bypass -Scope Process.

   Now run the following command:

   >
1. Paste the copied text into your shell and press Enter.
2. Wait a few seconds for the command to complete.
3. If you don't see any errors, you are ready to use Chocolatey! Type choco or choco -? now, or see Getting Started for usage instructions.

OCRMtPDF

 https://ocrmypdf.readthedocs.io/en/latest/installation.html#installing-on-windows

 

Installing on Windows¶

Native Windows¶

Note

Administrator privileges will be required for some of these steps.

You must install the following for Windows:

• Python 3.7 (64-bit) or later

• Tesseract 4.0 or later

• Ghostscript 9.50 or later

Using the Chocolatey package manager, install the following when running in an Administrator command prompt:

• choco install python3

• choco install --pre tesseract

• choco install ghostscript

• choco install pngquant (optional)

The commands above will install Python 3.x (latest version), Tesseract, Ghostscript and pngquant. Chocolatey may also need to install the Windows Visual C++ Runtime DLLs or other Windows patches, and may require a reboot.

You may then use pip to install ocrmypdf. (This can performed by a user or Administrator.):

• pip install ocrmypdf

Chocolatey automatically selects appropriate versions of these applications. If you are installing them manually, please install 64-bit versions of all applications for 64-bit Windows, or 32-bit versions of all applications for 32-bit Windows. Mixing the “bitness” of these programs will lead to errors.

OCRmyPDF will check the Windows Registry and standard locations in your Program Files for third party software it needs (specifically, Tesseract and Ghostscript). To override the versions OCRmyPDF selects, you can modify the PATH environment variable. Follow these directions to change the PATH.

Warning

As of early 2021, users have reported problems with the Microsoft Store version of Python and OCRmyPDF. These issues affect many other third party Python packages. Please download Python from Python.org or Chocolatey instead, and do not use the Microsoft Store version.