Changes for page Database Dumps

Last modified by Nikhil Singh on 2026/07/03 08:25

From version 1.1 >
edited by Nikhil Singh
on 2025/03/18 09:59
To version < 2.1
edited by Nikhil Singh
on 2026/07/03 08:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -DB Dumps
1 +Database Dumps
Content
... ... @@ -1,72 +1,6 @@
1 -=== **Step 1: Set Up the Environment** ===
1 +=== **Step 1: Execute the PowerShell Script** ===
2 2  
3 3  1. (((
4 -**Install Tortoise Git**:
5 -
6 -* Tortoise Git is a version control tool that will allow you to pull the latest scripts from your Git repository.
7 -* To install it:
8 -** Download and install Tortoise Git.
9 -)))
10 -1. (((
11 -**Create Folders**:
12 -
13 -* Open **File Explorer** on your PC and navigate to C:\.
14 -* Create the following folder structure:
15 -
16 -C:\EBsphere\devops\master
17 -
18 -* Inside C:\EBsphere\devops\master, you will store the latest scripts pulled from the Git repository.
19 -)))
20 -1. (((
21 -**Pull Latest Scripts Using Tortoise Git**:
22 -
23 -* Right-click on the master folder in **File Explorer**.
24 -* Select **TortoiseGit > Git Clone**.
25 -* Clone the repository if it's not already cloned, or choose **TortoiseGit > Pull** to pull the latest changes.
26 -* After pulling the latest updates, ensure the sql-script-db.ps1 script is available.
27 -)))
28 -
29 -----
30 -
31 -=== **Step 2: Set Up PowerShell 7.5** ===
32 -
33 -1. (((
34 -**Install PowerShell 7.5**:
35 -
36 -* If you do not have PowerShell 7.5 installed, download it from the [[PowerShell GitHub releases page>>url:https://github.com/PowerShell/PowerShell/releases/tag/v7.5.0]].
37 -* Install PowerShell 7.5 and ensure it's added to your system PATH.
38 -)))
39 -1. (((
40 -**Open PowerShell 7.5 in Administrator Mode**:
41 -
42 -* After installation, **right-click on PowerShell 7.5** and select **Run as Administrator**.
43 -)))
44 -1. (((
45 -**Set the Path to the Script Directory**:
46 -
47 -* In PowerShell, set the working directory to where the script is located (C:\EBsphere\devops\master\devops\sql):
48 -
49 -{{{
50 - }}}
51 -
52 -Set-Location -Path C:\EBsphere\devops\master\devops\sql
53 -)))
54 -1. (((
55 -**Check the PowerShell Version**:
56 -
57 -* Ensure you're using the correct version of PowerShell:
58 -
59 -{{{
60 - }}}
61 -
62 -$PSVersionTable.PSVersion
63 -)))
64 -
65 -----
66 -
67 -=== **Step 3: Execute the PowerShell Script** ===
68 -
69 -1. (((
70 70  **Prepare the Parameters**:
71 71  
72 72  * Set up the parameters needed for the script. These include:
... ... @@ -104,7 +104,7 @@
104 104  
105 105  ----
106 106  
107 -=== **Step 4: Validate the Results** ===
41 +=== **Step 2: Validate the Results** ===
108 108  
109 109  1. **Check in Azure Storage**:
110 110  1*. Go to your Azure Storage Account (use Azure portal or Azure Storage Explorer) and check if the necessary files (stored procedures, tables, functions, triggers, etc.) have been uploaded to the designated container.
... ... @@ -115,13 +115,15 @@
115 115  1*. Query the devops_sqlhashes table:
116 116  
117 117  {{{
118 - }}}(((
52 + }}}
53 +
54 +(((
119 119  SELECT * FROM devops_sqlhashes;
120 120  )))
121 121  
122 122  ----
123 123  
124 -=== **Step 5: Debugging (If Needed)** ===
60 +=== **Step 3: Debugging (If Needed)** ===
125 125  
126 126  * **Check Logs**: If the process didn't work as expected, look for any logs generated by the script or check the Azure logs for any issues during the file upload.
127 127  * **Error Messages**: Review any error messages printed to the PowerShell console or Microsoft Edge window for debugging.

Need help?

If you need help with XWiki you can contact: