I’ve taken the script by Jorge Klein to automate scaling of Azure SQL Databases and updated it with the following changes - Use Managed identities instead of Azure Automation Run As account Use Az moduled instead of AzureRM 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 <# .

WHAT HAPPENED? Recently while using the Delete Activity to delete files on an SFTP, I had this error(below) which wasn’t too helpful. The error message is very generic and took me sometime to figure out what was going on. If you are suffering from the same error then read on. ADF Delete Activity Error A little background on my process - I was trying to delete all files in a directory on the SFTP after I’ve processed the files.

Ever walked into a new job and find that you can’t make sense of any of the databases and how they all hang together? The answer to that question is probably YES (a million times YESSS)! This is where proper database organization comes in. So, let’s go into why this is important, what we can do prevent this for our future selves, and how to implement this. WHY? I think it’s pretty evident that having a messy database is not only stressful to maintain and work on, but it also creates a lot of risk for the business.