FAQ:NewInstanceMsSql Windows: Difference between revisions

From Wiki_dbSQWare
Jump to navigation Jump to search
← Older edit
No edit summary
 
(27 intermediate revisions by 2 users not shown)
Line 9: Line 9:
Use the portions that apply to your environment, and choose either the automatic or manual method as desired<br>
Use the portions that apply to your environment, and choose either the automatic or manual method as desired<br>


===General operating procedure for integrating a new MySQL/MariaDB instance===
===General operating procedure for integrating a new Sql-Server instance===
There will potentially be one or two connection cases to handle.
There is only the case of remote connection to handle. We make an SQL connection from mssql@sqwarebox via FreeTds (OpenSource TDS connection client).
* "local" for Unix machines (or those with Cygwin) where you'll be running MySQL/MariaDB on the machine hosting the instance (SSH connection from dbsqware@sqwarebox).
* "remote" for cases where you don't have SSH access to the machine (Windows, RDS, etc.).


Classic steps:
Classic steps:


*Setting up the environment
*Setting up the environment
*Checking system prerequisites for the "local" part (bash + rsync)


*Manual tests
*Manual tests
Line 26: Line 22:
You will see that these steps can be handled one by one or in batches!
You will see that these steps can be handled one by one or in batches!


==Integration of an MySQL/MariaDB instance==
==Integration of an SQL-server instance==


===Setting up the environment===
===Setting up the environment===
Line 33: Line 29:


=====Explanation of "DbAlias" (the unique dbSQWare key)=====
=====Explanation of "DbAlias" (the unique dbSQWare key)=====
The dbSQWare key must be unique and consistent with what has been configured for the gvsqw_DbAlias variable in sqwmys_GlobalVar.cfg!<br/>
The dbSQWare key must be unique and must match the entry configured in the freetds.conf file to connect to the instance.
We'll use a variable, MYSQL_SID, which has no value for MySQL/MariaDB but will identify the instance in dbSQWare.<br/>
Generally, when there is no named instance, we use the name of the Windows host that holds the instance. When there is a named instance, we concatenate the name of the Windows host and the instance name, separated by an underscore (do not use a backslash, we are on Linux!)."<br/>
By convention, we often use MYS "_" APPLI "_" ENV.<br/>
Examples :
Example: MYS_THISAPPS_PRD or MYS_THISOTHERAPPS_DEV ...<br/>
*WINMSQ => WINMSQ (status ON)
But nothing is imposed; you choose what "suits you"! You just need to set the MYSQL_SID variable in the MySQL account profile with the desired value.<br/>
*WINMSQ\INST1 => WINMSQ_INST1 (status ON)


=====Explanation of statuses=====
=====Explanation of statuses=====
*An "open" instance will be handled in "local" mode, meaning we will connect with mysql locally on the machine hosting the instance (ssh access from dbsqware@sqwarebox), status "ON".<br/>
Classically, for SQL Server, the status is 'ON'<br/>
*An instance where we don’t have local unix access will be managed in "remote" mode (like Windows, RDS, ...), status "DIST".<br/>
The 'OFF' status makes the instance disappear from the web view.<br/>
*The "OFF" status makes the instance "disappear" from the web view.<br/>
The 'NEW' status is used as an intermediate status between the beginning and the end of setting up a new instance.<br/>
*The "NEW" status is used as an intermediate status between the beginning and the end of setting up a new instance.<br/>
All other statuses allow the instance to be displayed in the repository (especially 'KEEP'), but they will not be taken into account by the automatic processes."<br/>
*All other statuses allow the instance to be displayed in the repository (especially "KEEP") but will not be taken into account by the automatic processes.<br/>
<br/>
<br/>
Resume of statuses :<br/>
Resume of statuses :<br/>
Line 54: Line 49:
| ON
| ON
| locale under Unix (the most common)
| locale under Unix (the most common)
|-
| DIST
| remote-only management
|-
|-
| KEEP
| KEEP
Line 80: Line 72:
[[File:AjoutInstance.png||admin|Ajout d'une instance]]
[[File:AjoutInstance.png||admin|Ajout d'une instance]]
[[File:DuplicateInstance.png||admin|Ajout par duplication d'une instance]]<br/>
[[File:DuplicateInstance.png||admin|Ajout par duplication d'une instance]]<br/>
[[File:DeclarationInstanceMySQL.png|admin|Add a new instance by duplicate an other one.]]<br/>
[[File:DeclarationInstanceMsSql.png|admin|Add a new instance by duplicate an other one.]]<br/>
Explanation of the fields :<br/>
Explanation of the fields :<br/>
{| align="center" {{Prettytable}}
{| align="center" {{Prettytable}}
Line 138: Line 130:
</syntaxhighlight>
</syntaxhighlight>


===Specific procedure for the "local" part (status ON)===
====Creating the Connection to the SQL Instance====
/!\ Only instances that will be in the "ON" status !<br/>
You have two options for connecting dbSQWare to your SQL Server instances:
 
* Creating an SQL account within the instance requires that mixed login be enabled.
====Verification of system prerequisites for the "local" part (bash + rsync)====
* Using a service account (declared in Active Directory).
Since SQWareProduction is mainly written in bash shell and synchronized from SQWareCentral using rsync, we therefore need "bash" and "rsync" to be installed !
====Creating a Specific dbSQWare SQL Server Account====
 
/!\ SQL access must be authorized on the instances if it is not already enabled!<br/>
=====Verification=====
Example creation order :
Adapt to your username and machine name.<br>
<syntaxhighlight lang="sql" line>
<br>
USE [master]
bash:
GO
<syntaxhighlight lang="sh" line>
CREATE LOGIN [msq_dba] WITH PASSWORD=N'NePasMettreCePassword!', DEFAULT_DATABASE=[master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
# From : mysql@my_mysql_host
GO
type bash
EXEC master..sp_addsrvrolemember @loginame = N'msq_dba', @rolename = N'sysadmin'
#or
GO
which bash
</syntaxhighlight>
rsync:
<syntaxhighlight lang="sh" line>
# From : mysql@my_mysql_host
type rsync
#or
which rsync
</syntaxhighlight>
</syntaxhighlight>
'sysadmin' is mandatory, particularly because of the commands "DBCC".


=====Installation=====
You can use any username and password you like!<br/>
Adapt to your machine type (use sudo if you are not root).<br/>
This account must be registered under the Unix account mssql@sqwarebox...<br/>
<br>
If a specific entry is found, it will be used; otherwise, the "DEFAULT" entry will be used.<br/>
RedHat / CentOS / ... :
<syntaxhighlight lang="sh" line># From : root@my_mysql_host
yum install -y bash rsync
#or
dnf install -y bash rsync</syntaxhighlight>
Ubuntu / Debian / ... :
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
 
mssql@sqwarebox:/home/mssql (NoSID) $ cat .passwd_mssql
# From : root@my_mysql_host
DEFAULT;msq_dba;NePasMettreCePassword!
apt install -y bash rsync
SPECIFIC_MSSQL;sa;sapass
</syntaxhighlight>
</syntaxhighlight>


====Unix user modification====
====Creating a connection with a specific dbSQWare service account====
Adapt to your machine type (sudo if you're not root).
Example of creation order :
Modify the homedir (not mandatory, but avoids ending up in /var/lib/mysql):
<syntaxhighlight lang="sh" line>
# From : root@my_mysql_host
mkdir -p /home/mysql
chown mysql:mysql /home/mysql
chmod 750 /home/mysql
</syntaxhighlight>
 
<syntaxhighlight lang="sh" line>
##Stop instance (service mysql/mariadb stop -- or -- systemctl stop mysql/mariadb)
usermod -d /home/mysql mysql -s /bin/bash
##Start instance (service mysql/mariadb start -- or -- systemctl start mysql/mariadb)
 
#Or directly vi /etc/passwd !
example : mysql:x:1004:989::/home/mysql:/bin/bash
</syntaxhighlight>
 
Assign a passwd to the mysql user (otherwise the key exchange connection will not work!):<syntaxhighlight lang="sh" line>
# From : root@my_mysql_host
passwd mysql
</syntaxhighlight>
 
====Creating a specific MySQL/MariaDB account for dbSQWare (for local connection)====
Adapt to your needs depending on what you want to do...<br/>
 
Example for local connection :
<syntaxhighlight lang="sql" line>
<syntaxhighlight lang="sql" line>
grant all privileges on *.* to 'DBSDBA'@'localhost' IDENTIFIED BY 'DoNotSetThisPassword!' with grant option;
USE [master]
 
GO
/* or */
CREATE LOGIN [domain\svc-dbsqware] FROM WINDOWS;
create user 'DBSDBA'@'localhost' IDENTIFIED BY 'DoNotSetThisPassword!';
GO
grant all privileges on *.* to 'DBSDBA'@'localhost' with grant option;
EXEC master..sp_addsrvrolemember @loginame = N'domain\svc-dbsqware', @rolename = N'sysadmin'
GO
</syntaxhighlight>
</syntaxhighlight>
 
<br/>
The 'sysadmin' account is mandatory, particularly due to the "DBCC" commands.<br/>
<br/>
This account must be registered under the Unix account mssql@sqwarebox... <br/>
If a specific entry is found, it is used; otherwise, the "DEFAULT" entry is used.<br/>
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
# From : mysql@my_mysql_host
mssql@sqwarebox:/home/mssql (NoSID) $ cat .passwd_mssql
#Then, create the .my.cnf file to allow connection without using passwd
DEFAULT;domain\svc-dbsqware;DoNotSetThisPassword!
echo "[client]
SPECIFIC_MSSQL;sa;sapass
password = DoNotSetThisPassword!
" >> $HOME/.my.cnf
chmod 600 $HOME/.my.cnf
</syntaxhighlight>
 
====Deployment of SSH key(s) from SQWareCentral to the target machine(s)====
There are two ways to proceed:
*An automatic one (from dbsqware@sqwarebox, but it requires you to know the password of the mysql Unix account)
*A manual one that you apply on each mysql Unix account
/!\ The password of your mysql Unix account must have been initialized, otherwise key-based authentication will not work!
 
=====Deployment of SSH key(s): batch method=====
<syntaxhighlight lang="sh" line># From : dbsqware@sqwarebox
menu_mys GenDeplSshKeys_SQWareCentral GenLstInstanceNew
</syntaxhighlight>
Verify that this is indeed the list you want to deploy, then choose option 1 ...<br/>
=> Enter the Unix password when prompted !
 
=====Deployment of SSH key(s): manual method=====
<syntaxhighlight lang="sh" line># From : mysql@my_mysql_host
if [ ! -r $HOME/.ssh/id_rsa ]
then
ssh-keygen -t rsa -N ''''''' -f $HOME/.ssh/id_rsa
fi
chmod go-w $HOME
echo "ssh-rsa AAAAB......XSPpdV11 dbsqware@sqwarebox" >>$HOME/.ssh/authorized_keys
chmod 700 $HOME/.ssh
chmod 600 $HOME/.ssh/authorized_keys
</syntaxhighlight>
=> Put the correct key in the "echo" (the one from dbsqware@sqwarebox)
 
====SSH connection test from SQWareCentral====
<syntaxhighlight lang="sh" line># From : dbsqware@sqwarebox
menu_mys TestSshConnection GenLstInstanceNew
</syntaxhighlight>
 
====Test of prerequisites on the target host (bash+rsync) via SSH from SQWareCentral====
<syntaxhighlight lang="sh" line># From : dbsqware@sqwarebox
menu_mys TestSysPrerequisites GenLstInstanceNew
</syntaxhighlight>
 
====Deployment of SQWareProduction====
<syntaxhighlight lang="sh" line># From : dbsqware@sqwarebox
 
#If deployment on "unique" user
menu_mys DeplScripts GenLstUniqueNew
 
#If deployment on "instance" user, the one specified in SQWareRepository
menu_mys DeplScripts GenLstInstanceNew
</syntaxhighlight>
</syntaxhighlight>


For "unique" user, it is the "standard" user. By default, we set it to "mysql", and it can be modified in SQWareCentral.
====Check the entry in freetds.conf====
 
We verify that the dbalias, host, and port information has been correctly entered in the file!<br/>
====Adding the dbSQWare environment to ~/.profile or ~/.bash_profile====
Once again, there are two ways to proceed:
 
*An automatic one (from dbsqware@sqwarebox)
*A manual one that you apply on each mysql Unix account
 
=====Adding the dbSQWare environment: batch method=====
<syntaxhighlight lang="sh" line># From : dbsqware@sqwarebox
menu_mys AdddbSQWareProfile GenLstInstanceNew
</syntaxhighlight>
Check that this is indeed the list you want to deploy, then choose 1 ...<br/>
=> In ~/.profile or ~/.bash_profile, change the following variable with the appropriate value: gvsqw_Env='XXX'
 
=====Adding the dbSQWare environment: manual method=====
Add the following lines to ~/.profile or ~/.bash_profile
<syntaxhighlight lang="sh" line># From : mysql@my_mysql_host
 
#dbSQWare
export gvsqw_MysBin=$HOME/SQWareProduction/mysql/bin
export gvsqw_Env='PRD'
lvsqw_IsTerminal=$(tty 2>&1 >/dev/null;echo $?)
if [ "$lvsqw_IsTerminal" = "0" ] && [ -r $gvsqw_MysBin/../etc/.profile_confort ]
then
. $gvsqw_MysBin/../etc/.profile_confort
fi
</syntaxhighlight>
 
=====Adding the variable MYSQL_SID=====
Add the MYSQL_SID variable in the ~/.profile or ~/.bash_profile
<syntaxhighlight lang="sh" line>
# From : mysql@my_mysql_host
export MYSQL_SID=MYS_INST_PRD
</syntaxhighlight>
 
====Test sendmail (Non mandatory)====
<syntaxhighlight lang="sh" line># From : dbsqware@sqwarebox
menu_mys TestSendmail GenLstInstanceNew
</syntaxhighlight>
 
===="Manual" connection test to the MySQL/MariaDB instance ("local" connection)====
/!\ Only instances that will be in "ON" status!
<syntaxhighlight lang="sh" line># From : dbsqware@sqwarebox
menu_mys TestInstConnectionOnNoMail GenLstInstanceNew
</syntaxhighlight>
 
===Specific Procedure for the "Remote" Port (DIST Status)===
 
====Creating a Specific MySQL/MariaDB Account (dbSQWare) (For Remote Connections)====
Example for a "Remote" Connection
<syntaxhighlight lang="sql" line>
grant all privileges on *.* to 'DBSDBA'@'%' IDENTIFIED BY 'DoNotSetThisPassword!' with grant option;
 
/* or */
create user 'DBSDBA'@'%' IDENTIFIED BY 'DoNotSetThisPassword!';
grant all privileges on *.* to 'DBSDBA'@'%' with grant option;
flush privileges;
</syntaxhighlight>
 
You can enter any username and password you like!<br/>
This account must be registered under the Unix account mysql@sqwarebox...<br/>
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
vi /home/mysql/.passwd_mysql
# with mssql@sqwarebox /applis/mssql/freetds/etc/freetds.conf
DbAlias;UserName;Passwd;HostName;Port
#Example
MYS_INST_PRD;DBSDBA;DoNotSetThisPassword!;srvdbmys01;3306
[WINMSQ_INST1]
host = WINMSQ
port = 1433
</syntaxhighlight>
</syntaxhighlight>


====Test "remote" connection====
====Test sendmail (not mandatory)====
/!\ Useful the first time, pointless afterwards because it's always the same machine !
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
# From : dbsqware@sqwarebox
# From : dbsqware@sqwarebox
menu_mys TestInstConnectionDistNoMail GenLstInstanceNew
menu_msq TestSendmail GenLstInstanceNew
</syntaxhighlight>
</syntaxhighlight>


==Starting the Instance==
===Manual Connection Tests to the SQL Server Instance===
===Generating the Default SQWareProduction Configuration===
The goal is to test the automatic connection to the SQL Server instance.
/!\ Only instances that will be in "ON" status!
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
# From : dbsqware@sqwarebox
# From : dbsqware@sqwarebox
menu_mys GenDefConf_SQWareProduction GenLstInstanceNew
menu_msq TestInstConnectionOnNoMail GenLstInstanceNew
</syntaxhighlight>
</syntaxhighlight>


===Update SQWare Repository===
Verify that you are connected to the correct instance (FullName field).<br/>
In the dbSQWare repository via the administration console, update the status of the new MySQL/MariaDB instance (currently NEW) to the desired value (ON, DIST).
Example:
############################################################################
TestType;InstanceParam;DbAlias;FullName;VersionMajInt;VersionPatch;ProductEdition;BackupPath
TestConnection;MSSQL_INST1;MSSQL_INST1;MSSQL\INST1;2008;10.50.1600.1;Developer;E:/BackupsMssql
############################################################################


===Testing the "Recovery" of Indicators===
If your Windows Server version is Windows Server 2012 or earlier, you must add "tds version = 7.0" to the Custom 2 column of the repository. This forces the use of a FreeTDS version compatible with the server.
At this point, you can test the recovery of missing indicators (in principle, only the instances you have just integrated!).
 
==Instance deployment==
===Generating the default SQLwareProduction configuration===
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
# From : dbsqware@sqwarebox
# From : dbsqware@sqwarebox
## for those with status "ON"
menu_msq GenDefConf_SQWareProduction GenLstInstanceNew
repind_mys
## for those with status "DIST"
repind_mys_dist
</syntaxhighlight>
</syntaxhighlight>


===Operation (stats, backups, etc.) for "ON" instances===
===Updating SQWareRepository===
====Generating SQWareProduction configs====
In the dbSQWare repository via the administration console, update the status of the new SQL Server instance (currently NEW) to '''ON'''.
If you followed the instance insertion procedure, this part is already done by step "menu_mys GenDefConf_SQWareProduction GenLstInstanceNew".<br/>
You can check with the next chapter.<br/>
<br/>
Connect to the machine that has the “MySQL/MariaDB” instance and type the following commands: <br/>
<syntaxhighlight lang="sh" line>
# From dbsqware@vmyswarebox
c MYS_INST_PRD
</syntaxhighlight>


===Testing the "recovery" of indicators===
At this point, you can test the recovery of missing indicators (generally, only the instances you just integrated!).
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
#Source de l'env si multi-instance (from mysql@my_mysql_host)
# From : dbsqware@sqwarebox
e MYS_INST_PRD
repind_msq
</syntaxhighlight>
</syntaxhighlight>


===Exploitation (stats, backups, …)===
====Generating SQLite Production Configurations====
If you followed the instance insertion procedure, this part is already done by the step "menu_msq GenDefConf_SQWareProduction GenLstInstanceNew".<br/>
You can verify this in the following chapter.<br/>
<br/> Connect to the central point's Unix machine with the "mssql" account and type the following commands:<br/>
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
# From mssql@vmsqwarebox
#Enter the instance name
too
too
./sqwmys_GenerateCreateInstance.ksh -dbsOnly
./sqwmsq_GenerateCreateInstance.ksh -I WINMSQ_INST1
</syntaxhighlight>
</syntaxhighlight>
Vérifier que ce qui est proposé est bon et tapez « y » si c’est le cas.<br/>
Verify that the proposed option is correct and type "y" if it is.<br/>  
A ce moment, vous avez généré les fichiers de configuration par défaut de SQWareProduction.
At this point, you have generated the default configuration files for SQWareProduction.


====Explanations====
====Explanations====
The previous steps created some default files. ($HOME/MYS_INST_PRD/sqwConfig)
The previous steps created some default files. ($HOME/admin/WINMSQ_INST1/sqwConfig)
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
#Enter the instance name
#Enter the instance name
e MYS_INST_PRD
e WINMSQ_INST1
cfg
cfg
cat sqwmys_Jobs.cfg
cat sqwmsq_Jobs.cfg
</syntaxhighlight>
</syntaxhighlight>


Line 398: Line 253:
#############################################
#############################################
#IndicDba: Gather DBAs indicators
#IndicDba: Gather DBAs indicators
IndicDba:$gvsqw_MysBin/sqwmys_GatherIndicators.ksh -I MYS_INST_PRD
IndicDba:$gvsqw_MsqBin/sqwmsq_GatherIndicators.ksh -I WINMSQ_INST1
 
#RotateErrorLog: Rotate error log
RotateErrorLog:$gvsqw_MsqBin/sqwmsq_RotateErrorLog.ksh -I WINMSQ_INST1 -Exec
 
#BackupAll: backup all databases
BackupAll:$gvsqw_MsqBin/sqwmsq_BackupAllDatabases.ksh -I WINMSQ_INST1 -Exec
 
#BackupAllRep: run failed backups from BackupAll
BackupAllRep:$gvsqw_MsqBin/sqwmsq_BackupAllDatabases.ksh -I WINMSQ_INST1 -REP -Exec


#Dump: backup all databases with mysqlDump
#StatisticsAll : update statistics tables for all databases
Dump:$gvsqw_MysBin/sqwmys_DumpAllDatabases.ksh -I MYS_INST_PRD -Exec
StatisticsAll:$gvsqw_MsqBin/sqwmsq_StatisticsAllDatabases.ksh -I WINMSQ_INST1 -Exec


#Optimize : optimize tables for all databases
#RebuildAll : Rebuild indexes tables for all databases
Optimize:$gvsqw_MysBin/sqwmys_OptimizeAllDatabases.ksh -I MYS_INST_PRD -Exec
RebuildAll:$gvsqw_MsqBin/sqwmsq_RebuildIndexAllDatabases.ksh -I WINMSQ_INST1 -Exec


#Analyse : analyze tables for all databases
#RestoreParfile : restore list of databases content in parfile
Analyze:$gvsqw_MysBin/sqwmys_AnalyzeAllDatabases.ksh -I MYS_INST_PRD -Exec
RestoreParfile:$gvsqw_MsqBin/sqwmsq_RestoreAllDatabases.ksh -I WINMSQ_INST1 -PAR $Parfile -Exec


#XtraFull: Backup full with XtraBackup
#CheckdbAll : DBCC CheckDB for all databases
XtraFull:$gvsqw_MysBin/sqwmys_XtraBackup.ksh -I MYS_INST_PRD -Type full -Exec
CheckdbAll:$gvsqw_MsqBin/sqwmsq_CheckdbAllDatabases.ksh -I WINMSQ_INST1 -Exec
</syntaxhighlight>


#XtraInc: Backup incremental with XtraBackup
This is a configuration file used by the sqwmsq_RunJob.ksh script to execute actions.<br/>
XtraInc:$gvsqw_MysBin/sqwmys_XtraBackup.ksh -I MYS_INST_PRD -Type inc -Exec
<br/>
File for a default cron job: $HOME/CrontabRef_WINMSQ_INST1 :
<syntaxhighlight lang="sh" line>
## mm(0-59) hh(0-23) dd(1-31) MM(0-12) DAY(0-sunday, 1-monday, ...) command
## WINMSQ_INST1
# Backup all databases
00 22 * * 1-6  bash -c '. $HOME/.profile ;$gvsqw_MsqBin/sqwmsq_RunJob.ksh -I WINMSQ_INST1 -A BackupAll > $HOME/tmp/BackupAll_WINMSQ_INST1.log 2>&1'
# Rebuild all databases
30 07 * * 6  bash -c '. $HOME/.profile ;$gvsqw_MsqBin/sqwmsq_RunJob.ksh -I WINMSQ_INST1 -A RebuildAll > $HOME/tmp/RebuildAll_WINMSQ_INST1.log 2>&1'
# Stats all databases
00 07 * * 0  bash -c '. $HOME/.profile ;$gvsqw_MsqBin/sqwmsq_RunJob.ksh -I WINMSQ_INST1 -A StatisticsAll > $HOME/tmp/StatisticsAll_WINMSQ_INST1.log 2>&1'
</syntaxhighlight>


#MariaFull: Backup full with MariaBackup
====Setting the backup path====
MariaFull:$gvsqw_MysBin/sqwmys_MariaBackup.ksh -I MYS_INST_PRD -Type full -Exec
On the instance to be managed, see the backup path in the registry key :
<syntaxhighlight lang="sql" line>
DECLARE  @v_regvalue varchar(256)
EXEC xp_instance_regread N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'BackupDirectory',  @v_regvalue OUTPUT
select 'lvsqw_BackupPath='+rtrim(@v_regvalue)+'='
go
</syntaxhighlight>


#MariaInc: Backup incremental with MariaBackup
To modify the path, the scripts rely on the registry key :
MariaInc:$gvsqw_MysBin/sqwmys_MariaBackup.ksh -I MYS_INST_PRD -Type inc -Exec
<syntaxhighlight lang="sql" line>
EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'BackupDirectory', REG_SZ, N'E:\Backups_db'
go
</syntaxhighlight>


#PurgeAlert: Rotate error log
Backup test with master :
PurgeAlert:$gvsqw_MysBin/sqwmys_PurgeAlert.ksh -I MYS_INST_PRD
<syntaxhighlight lang="sh" line>
#From mssql@vmsqwarebox
$gvsqw_MsqBin/sqwmsq_BackupDatabase.ksh -I WINMSQ_INST1 -D master -Type full -Exec
</syntaxhighlight>
</syntaxhighlight>


This is a configuration file used by the sqwmys_RunJob.ksh script to execute actions.<br/>
/!\ Be careful with this part; if you're not sure, don't do anything :
<br/>
File for a default cron job $HOME/CrontabRef_MYS_INST_PRD:
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
## mm(0-59) hh(0-23) dd(1-31) MM(0-12) DAY(0-sunday, 1-monday, ...) command
#From mssql@vmsqwarebox pour passer toutes les databases en 'RECOVERY SIMPLE'
## MYS_INST_PRD
$gvsqw_MsqBin/../tools/sqwmsq_AlterDatabaseRecoverySimple.ksh -I WINMSQ_INST1 -Exec
#Purge alert
 
00 08 * * 0 bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A PurgeAlert > $HOME/tmp/PurgeAlert_MYS_INST_PRD.log 2>&1'
#From mssql@vmsqwarebox pour modifier l'autogrowth toutes les logs de % en Mo
# Dump
$gvsqw_MsqBin/../tools/sqwmsq_AlterDatabaseModifyLogGrowth.ksh -I WINMSQ_INST1 -Exec
00 20 * * * bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A Dump > $HOME/tmp/Dump_MYS_INST_PRD.log 2>&1'
 
# Optimize
#From mssql@vmsqwarebox faire un SHRINK de toutes les logs
00 04 * * 6 bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A Optimize > $HOME/tmp/Optimize_MYS_INST_PRD.log 2>&1'
$gvsqw_MsqBin/../tools/sqwmsq_AlterDatabaseShrinkLogs.ksh -I WINMSQ_INST1 -Exec
# Analyze
00 05 * * 6 bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A Analyze > $HOME/tmp/Analyze_MYS_INST_PRD.log 2>&1'
# XtraBackup
#00 21 * * 6  bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A XtraFull > $HOME/tmp/XtraFull_MYS_INST_PRD.log 2>&1'
#00 21 * * 1-5 bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A XtraInc > $HOME/tmp/XtraInc_MYS_INST_PRD.log 2>&1'
# MariaBackup
#00 21 * * 6  bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A MariaFull > $HOME/tmp/MariaFull_MYS_INST_PRD.log 2>&1'
#00 21 * * 1-5 bash -c '. $HOME/.profile MYS_INST_PRD;$gvsqw_MysBin/sqwmys_RunJob.ksh -I MYS_INST_PRD -A MariaInc > $HOME/tmp/MariaInc_MYS_INST_PRD.log 2>&1'
</syntaxhighlight>
</syntaxhighlight>


====Startup====
====Deployment====
Setting up cron:
Setting up the cron :
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
mv $HOME/CrontabRef_MYS_INST_PRD $HOME/CrontabRef
crontab -l > $HOME/CrontabRef
vi $HOME/CrontabRef_WINMSQ_INST1
cat $HOME/CrontabRef_WINMSQ_INST1 >> $HOME/CrontabRef
vi $HOME/CrontabRef
vi $HOME/CrontabRef
crontab $HOME/CrontabRef
crontab $HOME/CrontabRef
Line 456: Line 335:
</syntaxhighlight>
</syntaxhighlight>


Update the file CrontabRef  :
Updating the CrontabRef file :
<syntaxhighlight lang="sh" line>
<syntaxhighlight lang="sh" line>
crontab -l > $HOME/CrontabRef
crontab -l > $HOME/CrontabRef
Line 463: Line 342:


====Useful commands====
====Useful commands====
alias :
Interesting aliases :
e DBALIAS => source env for the instance
e DBALIAS => Load the environment for the instance
bin, etc, too ... => to go to the standard SQWareProduction tree
bin, etc, too ... => To navigate to the standard SQWareProduction directory
cbin, cetc, ctoo ... => to go to the custom SQWareProduction tree
cbin, cetc, ctoo ... => To navigate to the custom SQWareProduction directory
log => SQWareProduction logs
log => logs SQWareProduction
dmp => go to the backup paths


Some script options:
Some script options :
-h => online help
-h => aide en ligne
-s => online examples
-s => exemples en ligne
-Exec => when present; if not set, only outputs commands without executing them.
-Exec => lorsque elle est présente, si non settée ne sort que les commandes sans les exécuter


Examples :
Examples :
  mysql@my_mysql_host:$HOME/admin/MYS_INST_PRD/logs/DumpAllDatabases (MYS_DBA_PRD) $ bin
  mssql@HOSTCENTRAL:$HOME/admin/WINMSQ_INST1/logs/StatisticsDatabase (WINMSQ_INST1) $ bin
  total 100
  total 112
  drwxr-x---  2 dbsqware dba 4096 Sep 6 14:09 .
  drwxr-x---  2 dbsqware dba 4096 Sep 25 21:22 .
  drwxr-x--- 15 dbsqware dba  187 Aug 16 15:50 ..
  drwxr-x--- 15 dbsqware dba  4096 Sep 25 21:22 ..
  -rwxr-x---  1 dbsqware dba 2957 Aug 16 15:50 sqwmys_AnalyzeAllDatabases.ksh
  -rwxr-x---  1 dbsqware dba 10858 Sep 25 21:22 sqwmsq_BackupAllDatabases.ksh
  -rwxr-x---  1 dbsqware dba 2514 Aug 16 15:50 sqwmys_AnalyzeDatabase.ksh
  -rwxr-x---  1 dbsqware dba  6013 Sep 25 21:22 sqwmsq_BackupDatabase.ksh
  -rwxr-x---  1 dbsqware dba 2608 Aug 16 15:50 sqwmys_CheckAllDatabases.ksh
  -rwxr-x---  1 dbsqware dba  7663 Sep 25 21:22 sqwmsq_CheckdbAllDatabases.ksh
  -rwxr-x---  1 dbsqware dba 2257 Aug 16 15:50 sqwmys_CheckDatabase.ksh
  -rwxr-x---  1 dbsqware dba  4809 Sep 25 21:22 sqwmsq_CheckdbDatabase.ksh
  -rwxr-x---  1 dbsqware dba 5418 Aug 16 15:50 sqwmys_CopyDumpAllDatabases.ksh
  ...
-rwxr-x---  1 dbsqware dba 5324 Aug 16 15:50 sqwmys_CopyDumpDatabase.ksh
  -rwxr-x---  1 dbsqware dba 5610 Sep 6 10:45 sqwmys_CopyMariaBackup.ksh
-rwxr-x---  1 dbsqware dba 5594 Sep 6 14:08 sqwmys_CopyXtraBackup.ksh
-rwxr-x---  1 dbsqware dba 3248 Aug 16 15:50 sqwmys_DumpAllDatabases.ksh
-rwxr-x---  1 dbsqware dba 3541 Aug 16 15:50 sqwmys_DumpDatabase.ksh
lrwxrwxrwx  1 dbsqware dba  36 Jan  2  2022 sqwmys_ExecSQL.ksh -> ../../generic/bin/sqwgen_ExecSQL.ksh
-rwxr-x---  1 dbsqware dba 2455 Aug 16 15:50 sqwmys_GatherIndicators.ksh
-rwxr-x---  1 dbsqware dba 2454 Aug 16 15:50 sqwmys_GatherStructure.ksh
-rwxr-x---  1 dbsqware dba 3043 Aug 16 15:50 sqwmys_MariaBackup.ksh
lrwxrwxrwx  1 dbsqware dba  38 Jan  2  2022 sqwmys_NetBackup.ksh -> ../../generic/bin/sqwgen_NetBackup.ksh
-rwxr-x---  1 dbsqware dba 2959 Aug 16 15:50 sqwmys_OptimizeAllDatabases.ksh
-rwxr-x---  1 dbsqware dba 2522 Aug 16 15:50 sqwmys_OptimizeDatabase.ksh
lrwxrwxrwx  1 dbsqware dba  40 Jan  2  2022 sqwmys_ParallelRun.ksh -> ../../generic/bin/sqwgen_ParallelRun.ksh
-rwxr-x---  1 dbsqware dba 2252 Aug 16 15:50 sqwmys_PurgeAlert.ksh
-rwxr-x---  1 dbsqware dba 3855 Aug 16 15:50 sqwmys_RestoreAllDatabases.ksh
-rwxr-x---  1 dbsqware dba 3463 Aug 16 15:50 sqwmys_RestoreDatabase.ksh
-rwxr-x---  1 dbsqware dba 3825 Aug 16 15:50 sqwmys_RotateLogSlowQuery.ksh
lrwxrwxrwx  1 dbsqware dba  40 Jan  2  2022 sqwmys_RsyncBackup.ksh -> ../../generic/bin/sqwgen_RsyncBackup.ksh
  lrwxrwxrwx  1 dbsqware dba  35 Jan  2  2022 sqwmys_RunJob.ksh -> ../../generic/bin/sqwgen_RunJob.ksh
-rwxr-x---  1 dbsqware dba 3025 Aug 16 15:50 sqwmys_XtraBackup.ksh


  mysql@my_mysql_host:$HOME/SQWareProduction/mysql/bin (MYS_INST_PRD) $  
  mssql@HOSTCENTRAL:$HOME/SQWareProduction/mssql/bin (WINMSQ_INST1) $  
  ./sqwmys_DumpAllDatabases.ksh -h
  ./sqwmsq_StatisticsAllDatabases.ksh -h
   
   
  Sourcing sqwmys_Global.lib v2023.06 SQWareProduction for MySQL (dbSQWare) ...
  Sourcing sqwmsq_Global.lib v2021.02 SQWareProduction for MsSql ...
   
   
  Usage: sqwmys_DumpAllDatabases.ksh [-h] -I instance [+ options]
  Usage: sqwmsq_StatisticsAllDatabases.ksh [-h] -S|-I <FreeTdsAlias> [+ options]
   
   
  DESCRIPTION
  DESCRIPTION
     sqwmys_DumpAllDatabases.ksh dump databases in parallel
     sqwmsq_StatisticsAllDatabases.ksh update Statistics databases in //
  SUPPORT
  SUPPORT
     MySql  supported versions: 5.0 <= v <= 8
     MsSql supported versions: 2000 <= v <= 2019
    MariaDB supported versions: 5.5 <= v <= 11.6
   
   
  PARAMETERS
  PARAMETERS
       -I  instance      : Target instance to mysqldump.
       -S|-I  Instance    : Target instance (freeTds alias).
  OPTIONS
  OPTIONS
       -h help           : Display the full usage.
       -h   help         : Display the full usage.
       -s                : Display samples of usage.
       -s                : Display samples of usage.
       -P Nb threads    : Number of threads in parallel (by default 2).
       -P   Nb_threads    : Number of threads in parallel (by default 4).
      -RD directory      : Directory to write dump file (default /backups/mysql/$MYSQL_SID).
       -ID listdb       : Databases list to include.
       -ID listdb         : List of databases to be dumped (by default all).
       -ED listdb       : Databases list to exclude.
       -ED listdb         : List of databases to exclude from dump.
       -IL likeclause   : Like clause to generate databases list (example: 'db%').
       -IL likeclause     : Like clause to generate databases list (example: 'db%').
       -EL likeclause   : Like clause to exclude databases (example: 'nodb%').
       -EL likeclause     : Like clause to exclude databases (example: 'nodb%').
       -WCD whereclause   : Where clause to generate databases list.
      -HI Nb_Generations : Number of generations to keep (by default 2).
       -FRT return_code   : Force return code value on error.
       -WCD whereclause : Where clause to generate databases list.
       -AddMail email    : Email Address to add at 'xxx'.
      -AGR  Nb sec      : Nb of seconds between two runs (by default 1s).
      -AGE  Nb sec      : Nb of seconds between two checks of end (by default 10s).
       -FRT return_code : Force return code value on error.
      -Opt  option      : Additional options for mysqldump.
      -Dist              : For distant connection to database (change $gvsqw_ConnectString to $gvsqw_DistConnectString ).
       -AddMail email    : Email address to add at 'xxx'.
       -SendReport        : Send execution log report.
       -SendReport        : Send execution log report.
       -NoMail            : Deactivate sendmail on error xxx (by default, send on error).
       -PAR parfile      : Parfile file for databases list.
       -Locale  locale  : Force Locale for help display (fr,en).
      -AGR Nb_sec        : Nb of seconds between two run (by default 5s).
       -Consistent        : Lock for consistent mode (by default, no lock).
       -AGE Nb_sec        : Nb of seconds between two check of end (by default 5s).
       -NoMail            : Desactivate sendmail on error xxx (by default, send on error).
       -Exec              : Execute commands (default, display generated commands)
       -Exec              : Execute commands (default, display generated commands)


Enjoy !
Enjoy !

Latest revision as of 16:23, 5 December 2025

Generalties


Warning:
Before anything, don't go further if you don't have read the first section "dbSQWare Concepts " !.

In this chapter, we will consider that SQWareCentral has been installed on dbsqware@sqwarebox.

Limits of this section

This chapter only deals with adding a new instance to a base that is already configured and functional.
Use the portions that apply to your environment, and choose either the automatic or manual method as desired

General operating procedure for integrating a new Sql-Server instance

There is only the case of remote connection to handle. We make an SQL connection from mssql@sqwarebox via FreeTds (OpenSource TDS connection client).

Classic steps:

  • Setting up the environment
  • Manual tests
  • Deployment of the instance

You will see that these steps can be handled one by one or in batches!

Integration of an SQL-server instance

Setting up the environment

General

Explanation of "DbAlias" (the unique dbSQWare key)

The dbSQWare key must be unique and must match the entry configured in the freetds.conf file to connect to the instance. Generally, when there is no named instance, we use the name of the Windows host that holds the instance. When there is a named instance, we concatenate the name of the Windows host and the instance name, separated by an underscore (do not use a backslash, we are on Linux!)."
Examples :

  • WINMSQ => WINMSQ (status ON)
  • WINMSQ\INST1 => WINMSQ_INST1 (status ON)
Explanation of statuses

Classically, for SQL Server, the status is 'ON'
The 'OFF' status makes the instance disappear from the web view.
The 'NEW' status is used as an intermediate status between the beginning and the end of setting up a new instance.
All other statuses allow the instance to be displayed in the repository (especially 'KEEP'), but they will not be taken into account by the automatic processes."

Resume of statuses :

Status Description
ON locale under Unix (the most common)
KEEP temporary status, during maintenance for example or before complete deletion
NEW temporary status, during configuration
OFF visual removal of the instance (without deleting its configuration)
XXX not supported...

Instance declaration in SQWareRepository with SQWareWeb

We will declare the new instance from the SQWareWeb administration interface.
Admin dbSQWare


Declare the new instance with the status "NEW" (Add or Duplicate).
Ajout d'une instance Ajout par duplication d'une instance
Add a new instance by duplicate an other one.
Explanation of the fields :

Fields Description
Db Alias Unique key that identifies the instance in dbSQWare (no value for MySQL/MariaDB).
Dbms Name Type of SGBD
Virtual Host Virtual Host (same as Host if not clustered)

.

Host Name Hostname of the instance
User Name User associated with the instance
Port Listening port of the instance.
Comments A brief description of what the instance hosts
Status Instance status (see above for explanations).
Contact A contact if needed
Environnement Instance environment (PRD, PPR, REC, DEV, TST, ...)
Client Used only for filtering (enter a client name and/or department and/or service...)
GlobalHost Free field in which the hypervisor host is often entered, for example.
Custom1 Free field 1
Custom2 Free field 2
Regenerate the reference files of SQWareCentral.

Type the following command which will generate the reference files: 

# From : dbsqware@sqwarebox
gen_all

Creating the Connection to the SQL Instance

You have two options for connecting dbSQWare to your SQL Server instances:

  • Creating an SQL account within the instance requires that mixed login be enabled.
  • Using a service account (declared in Active Directory).

Creating a Specific dbSQWare SQL Server Account

/!\ SQL access must be authorized on the instances if it is not already enabled!
Example creation order : 

USE [master]
GO
CREATE LOGIN [msq_dba] WITH PASSWORD=N'NePasMettreCePassword!', DEFAULT_DATABASE=[master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
GO
EXEC master..sp_addsrvrolemember @loginame = N'msq_dba', @rolename = N'sysadmin'
GO

'sysadmin' is mandatory, particularly because of the commands "DBCC".

You can use any username and password you like!
This account must be registered under the Unix account mssql@sqwarebox...
If a specific entry is found, it will be used; otherwise, the "DEFAULT" entry will be used.

mssql@sqwarebox:/home/mssql (NoSID) $ cat .passwd_mssql
DEFAULT;msq_dba;NePasMettreCePassword!
SPECIFIC_MSSQL;sa;sapass

Creating a connection with a specific dbSQWare service account

Example of creation order : 

USE [master]
GO
CREATE LOGIN [domain\svc-dbsqware] FROM WINDOWS;
GO
EXEC master..sp_addsrvrolemember @loginame = N'domain\svc-dbsqware', @rolename = N'sysadmin'
GO


The 'sysadmin' account is mandatory, particularly due to the "DBCC" commands.

This account must be registered under the Unix account mssql@sqwarebox...
If a specific entry is found, it is used; otherwise, the "DEFAULT" entry is used.

mssql@sqwarebox:/home/mssql (NoSID) $ cat .passwd_mssql
DEFAULT;domain\svc-dbsqware;DoNotSetThisPassword!
SPECIFIC_MSSQL;sa;sapass

Check the entry in freetds.conf

We verify that the dbalias, host, and port information has been correctly entered in the file!

# with mssql@sqwarebox /applis/mssql/freetds/etc/freetds.conf
#Example
[WINMSQ_INST1]
	host = WINMSQ
	port = 1433

Test sendmail (not mandatory)

/!\ Useful the first time, pointless afterwards because it's always the same machine ! 

# From : dbsqware@sqwarebox
menu_msq TestSendmail GenLstInstanceNew

Manual Connection Tests to the SQL Server Instance

The goal is to test the automatic connection to the SQL Server instance. 

# From : dbsqware@sqwarebox
menu_msq TestInstConnectionOnNoMail GenLstInstanceNew

Verify that you are connected to the correct instance (FullName field).
Example: 

############################################################################
TestType;InstanceParam;DbAlias;FullName;VersionMajInt;VersionPatch;ProductEdition;BackupPath
TestConnection;MSSQL_INST1;MSSQL_INST1;MSSQL\INST1;2008;10.50.1600.1;Developer;E:/BackupsMssql
############################################################################

If your Windows Server version is Windows Server 2012 or earlier, you must add "tds version = 7.0" to the Custom 2 column of the repository. This forces the use of a FreeTDS version compatible with the server.

Instance deployment

Generating the default SQLwareProduction configuration

# From : dbsqware@sqwarebox
menu_msq GenDefConf_SQWareProduction GenLstInstanceNew

Updating SQWareRepository

In the dbSQWare repository via the administration console, update the status of the new SQL Server instance (currently NEW) to ON.

Testing the "recovery" of indicators

At this point, you can test the recovery of missing indicators (generally, only the instances you just integrated!). 

# From : dbsqware@sqwarebox
repind_msq

Exploitation (stats, backups, …)

Generating SQLite Production Configurations

If you followed the instance insertion procedure, this part is already done by the step "menu_msq GenDefConf_SQWareProduction GenLstInstanceNew".
You can verify this in the following chapter.

Connect to the central point's Unix machine with the "mssql" account and type the following commands:

# From mssql@vmsqwarebox
#Enter the instance name
too
./sqwmsq_GenerateCreateInstance.ksh -I WINMSQ_INST1

Verify that the proposed option is correct and type "y" if it is.
At this point, you have generated the default configuration files for SQWareProduction.

Explanations

The previous steps created some default files. ($HOME/admin/WINMSQ_INST1/sqwConfig) 

#Enter the instance name
e WINMSQ_INST1
cfg
cat sqwmsq_Jobs.cfg

#############################################
#IndicDba: Gather DBAs indicators
IndicDba:$gvsqw_MsqBin/sqwmsq_GatherIndicators.ksh -I WINMSQ_INST1

#RotateErrorLog: Rotate error log
RotateErrorLog:$gvsqw_MsqBin/sqwmsq_RotateErrorLog.ksh -I WINMSQ_INST1 -Exec

#BackupAll: backup all databases
BackupAll:$gvsqw_MsqBin/sqwmsq_BackupAllDatabases.ksh -I WINMSQ_INST1 -Exec

#BackupAllRep: run failed backups from BackupAll
BackupAllRep:$gvsqw_MsqBin/sqwmsq_BackupAllDatabases.ksh -I WINMSQ_INST1 -REP -Exec

#StatisticsAll : update statistics tables for all databases
StatisticsAll:$gvsqw_MsqBin/sqwmsq_StatisticsAllDatabases.ksh -I WINMSQ_INST1 -Exec

#RebuildAll : Rebuild indexes tables for all databases
RebuildAll:$gvsqw_MsqBin/sqwmsq_RebuildIndexAllDatabases.ksh -I WINMSQ_INST1 -Exec

#RestoreParfile : restore list of databases content in parfile
RestoreParfile:$gvsqw_MsqBin/sqwmsq_RestoreAllDatabases.ksh -I WINMSQ_INST1 -PAR $Parfile -Exec

#CheckdbAll : DBCC CheckDB for all databases
CheckdbAll:$gvsqw_MsqBin/sqwmsq_CheckdbAllDatabases.ksh -I WINMSQ_INST1 -Exec

This is a configuration file used by the sqwmsq_RunJob.ksh script to execute actions.

File for a default cron job: $HOME/CrontabRef_WINMSQ_INST1 : 

## mm(0-59) hh(0-23) dd(1-31) MM(0-12) DAY(0-sunday, 1-monday, ...) command
## WINMSQ_INST1
# Backup all databases
00 22 * * 1-6  bash -c '. $HOME/.profile ;$gvsqw_MsqBin/sqwmsq_RunJob.ksh -I WINMSQ_INST1 -A BackupAll > $HOME/tmp/BackupAll_WINMSQ_INST1.log 2>&1'
# Rebuild all databases
30 07 * * 6  bash -c '. $HOME/.profile ;$gvsqw_MsqBin/sqwmsq_RunJob.ksh -I WINMSQ_INST1 -A RebuildAll > $HOME/tmp/RebuildAll_WINMSQ_INST1.log 2>&1'
# Stats all databases
00 07 * * 0  bash -c '. $HOME/.profile ;$gvsqw_MsqBin/sqwmsq_RunJob.ksh -I WINMSQ_INST1 -A StatisticsAll > $HOME/tmp/StatisticsAll_WINMSQ_INST1.log 2>&1'

Setting the backup path

On the instance to be managed, see the backup path in the registry key : 

DECLARE  @v_regvalue varchar(256)
EXEC xp_instance_regread N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'BackupDirectory',  @v_regvalue OUTPUT
select 'lvsqw_BackupPath='+rtrim(@v_regvalue)+'='
go

To modify the path, the scripts rely on the registry key : 

EXEC xp_instance_regwrite N'HKEY_LOCAL_MACHINE', N'Software\Microsoft\MSSQLServer\MSSQLServer', N'BackupDirectory', REG_SZ, N'E:\Backups_db'
go

Backup test with master : 

#From mssql@vmsqwarebox
$gvsqw_MsqBin/sqwmsq_BackupDatabase.ksh -I WINMSQ_INST1 -D master -Type full -Exec

/!\ Be careful with this part; if you're not sure, don't do anything : 

#From mssql@vmsqwarebox pour passer toutes les databases en 'RECOVERY SIMPLE'
$gvsqw_MsqBin/../tools/sqwmsq_AlterDatabaseRecoverySimple.ksh -I WINMSQ_INST1 -Exec

#From mssql@vmsqwarebox pour modifier l'autogrowth toutes les logs de % en Mo
$gvsqw_MsqBin/../tools/sqwmsq_AlterDatabaseModifyLogGrowth.ksh -I WINMSQ_INST1 -Exec

#From mssql@vmsqwarebox faire un SHRINK de toutes les logs
$gvsqw_MsqBin/../tools/sqwmsq_AlterDatabaseShrinkLogs.ksh -I WINMSQ_INST1 -Exec

Deployment

Setting up the cron : 

crontab -l > $HOME/CrontabRef
vi $HOME/CrontabRef_WINMSQ_INST1
cat $HOME/CrontabRef_WINMSQ_INST1 >> $HOME/CrontabRef
vi $HOME/CrontabRef
crontab $HOME/CrontabRef
crontab -l

Updating the CrontabRef file : 

crontab -l > $HOME/CrontabRef
cat $HOME/CrontabRef

Useful commands

Interesting aliases : 

e DBALIAS => Load the environment for the instance
bin, etc, too ... => To navigate to the standard SQWareProduction directory
cbin, cetc, ctoo ... => To navigate to the custom SQWareProduction directory
log => logs SQWareProduction

Some script options : 

-h => aide en ligne
-s => exemples en ligne
-Exec => lorsque elle est présente, si non settée ne sort que les commandes sans les exécuter

Examples : 

mssql@HOSTCENTRAL:$HOME/admin/WINMSQ_INST1/logs/StatisticsDatabase (WINMSQ_INST1) $ bin
total 112
drwxr-x---  2 dbsqware dba  4096 Sep 25 21:22 .
drwxr-x--- 15 dbsqware dba  4096 Sep 25 21:22 ..
-rwxr-x---  1 dbsqware dba 10858 Sep 25 21:22 sqwmsq_BackupAllDatabases.ksh
-rwxr-x---  1 dbsqware dba  6013 Sep 25 21:22 sqwmsq_BackupDatabase.ksh
-rwxr-x---  1 dbsqware dba  7663 Sep 25 21:22 sqwmsq_CheckdbAllDatabases.ksh
-rwxr-x---  1 dbsqware dba  4809 Sep 25 21:22 sqwmsq_CheckdbDatabase.ksh
...

mssql@HOSTCENTRAL:$HOME/SQWareProduction/mssql/bin (WINMSQ_INST1) $ 
./sqwmsq_StatisticsAllDatabases.ksh -h

Sourcing sqwmsq_Global.lib v2021.02 SQWareProduction for MsSql ...

Usage: sqwmsq_StatisticsAllDatabases.ksh [-h] -S|-I <FreeTdsAlias> [+ options]

DESCRIPTION
   sqwmsq_StatisticsAllDatabases.ksh update Statistics databases in //
SUPPORT
   MsSql supported versions: 2000 <= v <= 2019

PARAMETERS
     -S|-I  Instance    : Target instance (freeTds alias).
OPTIONS
     -h   help          : Display the full usage.
     -s                 : Display samples of usage.
     -P   Nb_threads    : Number of threads in parallel (by default 4).
     -ID  listdb        : Databases list to include.
     -ED  listdb        : Databases list to exclude.
     -IL  likeclause    : Like clause to generate databases list (example: 'db%').
     -EL  likeclause    : Like clause to exclude databases (example: 'nodb%').
     -WCD whereclause   : Where clause to generate databases list.
     -FRT return_code   : Force return code value on error.
     -AddMail email     : Email Address to add at 'xxx'.
     -SendReport        : Send execution log report.
     -PAR parfile       : Parfile file for databases list.
     -AGR Nb_sec        : Nb of seconds between two run (by default 5s).
     -AGE Nb_sec        : Nb of seconds between two check of end (by default 5s).
     -NoMail            : Desactivate sendmail on error xxx (by default, send on error).
     -Exec              : Execute commands (default, display generated commands)

Enjoy !

Retrieved from "https://wiki.dbsqware.com/index.php?title=FAQ:NewInstanceMsSql_Windows&oldid=35586"