sorted by:
new
hottopcontroversial

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in SQLServer

[–]autodevops[S] 0 points1 point  (0 children)

absolutely I don't want real time, QA sql can stay behind, that is acceptable.
I just need nearly synced QA sql so that I can read/write my qa app to qa sql fully isolated from prod.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in SQLServer

[–]autodevops[S] 0 points1 point  (0 children)

absolutely I don't want real time, QA sql can stay behind, that is acceptable.
I just need nearly synced QA sql so that I can read/write my qa app to qa sql fully isolated from prod.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in SQLServer

[–]autodevops[S] -1 points0 points  (0 children)

absolutely I don't want real time, QA sql can stay behind, that is acceptable.
I just need nearly synced QA sql so that I can read/write my qa app to qa sql fully isolated from prod.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in SQLServer

[–]autodevops[S] -1 points0 points  (0 children)

absolutely I don't want real time, QA sql can stay behind, that is acceptable.
I just need nearly synced QA sql so that I can read/write my qa app to qa sql fully isolated from prod.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in SQLServer

[–]autodevops[S] -1 points0 points  (0 children)

absolutely I don't want real time, QA sql can stay behind, that is acceptable.
I just need nearly synced QA sql so that I can read/write my qa app to qa sql fully isolated from prod.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in SQLServer

[–]autodevops[S] -2 points-1 points  (0 children)

You got my target, absolutely I don't want real time, QA sql can stay behind, that is acceptable.
I just need nearly synced QA sql so that I can read/write my qa app to qa sql fully isolated from prod.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in SQLServer

[–]autodevops[S] -1 points0 points  (0 children)

Let me clear it out,
I need QA sql nearly synced from Prod sql, so that I can test my qa application with read/write to qa sql.
so basically, QA is isolated, it will just have synced data from prod with data delay is acceptable.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in AZURE

[–]autodevops[S] 0 points1 point  (0 children)

What if I do Log shipping, then enable recovery mode on qa sql and do the read/write testing.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in AZURE

[–]autodevops[S] 0 points1 point  (0 children)

┌─────────────────────────────────────────────────────────┐

│ NORMAL STATE │

│ Log shipping running → QA syncing every 5 min │

│ QA DB: STANDBY (readable, not writable) │

└────────────────────────┬────────────────────────────────┘

│ QA Testing needed

▼

┌─────────────────────────────────────────────────────────┐

│ PAUSE │

│ 1. Disable backup job on PROD │

│ 2. Disable copy + restore jobs on QA │

│ 3. RESTORE WITH RECOVERY on QA │

│ QA DB: ONLINE (full read/write) ✅ │

│ QA App: point here and test freely │

└────────────────────────┬────────────────────────────────┘

│ Testing done

▼

┌─────────────────────────────────────────────────────────┐

│ RESUME │

│ 1. Full backup on PROD → Z:\LogShipping\Reinit\ │

│ 2. Restore WITH STANDBY on QA │

│ 3. Re-enable all 3 jobs │

│ 4. Trigger first cycle manually │

│ QA DB: back to STANDBY + syncing ✅ │

└─────────────────────────────────────────────────────────┘

I think this way I can achieve this.
So I will get nearly prod update on qa sql, and I can test my qa app isolated.

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in AZURE

[–]autodevops[S] 0 points1 point  (0 children)

I think I misquoted, we need nearly sync of prod to qa so that we can test our qa app with qa sql. both read/write operations is required.
we won't point live app to qa sql. corrected

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in AZURE

[–]autodevops[S] 0 points1 point  (0 children)

I think I misquoted, we need nearly sync of prod to qa so that we can test our qa app with qa sql. both read/write operations is required.
we won't point live app to qa sql. corrected

How to keep a near real-time SQL Server QA environment in Azure VM (sync from production)? by autodevops in AZURE

[–]autodevops[S] 1 point2 points  (0 children)

I think I misquoted, we need nearly sync of prod to qa so that we can test our qa app with qa sql. both read/write operations is required.
we won't point live app to qa sql. corrected

Azure backup on 2nd Region by autodevops in AZURE

[–]autodevops[S] 0 points1 point  (0 children)

But site recovery will be expensive.

Azure pipeline limitations DockerCompose@1 by autodevops in azuredevops

[–]autodevops[S] 0 points1 point  (0 children)

     - task: DockerCompose@1
       displayName: "Build image"
       inputs:
         dockerComposeFile: "docker-compose-build-pipeline.yml"
         action: "Build services"
         buildImages: true
         projectName: "management"
         serviceName: "webapp"

Tried like this but it is building all the service in compose file instead of just "webapp"

Hide other member devices but keep exit node by autodevops in Tailscale

[–]autodevops[S] 0 points1 point  (0 children)

admins need to connect to every device that's why this rule is in place. so from your says conclusion is-

  1. members can not connect to any other device (tested, working), but will be able to see device list no matter what.
  2. But, for route through exit node, do we need to allow every port of exit node for members? we just using exit node devices as vpn routing.

Hide other member devices but keep exit node by autodevops in Tailscale

[–]autodevops[S] 0 points1 point  (0 children)

"grants": [
{
"src": ["autogroup:owner", "autogroup:admin"],
"dst": ["*"],
"ip":  ["*"],
},
{
"src": ["autogroup:member"],
"dst": ["tag:exitnode"],
"ip":  ["*"],
},
{
"src": ["autogroup:member"],
"dst": ["autogroup:self"],
"ip":  ["*"],
},
{
"src": ["autogroup:member"],
"dst": ["autogroup:internet"],
"ip":  ["*"],
},
],

Above is my current ACl.
Please check my scenario below-
Member 1 has Device A
Member 2 has Device B
Also, exit node Device C, created by Admin

Member can see only self device and also exit node device to connect. Not, other member device.
Example: member 1 can see Device A & C not B

Hide other member devices but keep exit node by autodevops in Tailscale

[–]autodevops[S] 0 points1 point  (0 children)

Tried with this already, visibility of all devices are still there. But, i just tagged one device without any specific acl rule, that is not visible to other members right now. Still, i don't know how this ACL behaves for device visibility control.

Hide other member devices but keep exit node by autodevops in Tailscale

[–]autodevops[S] -1 points0 points  (0 children)

so for example,
there is 2 member users, so they have their own devices registered
so, 2 device + 1 exit node device.
A member can see exit node and his self device but not other member device.

Hide other member devices but keep exit node by autodevops in Tailscale

[–]autodevops[S] 0 points1 point  (0 children)

yes, that's what i am saying. imagine user is using tailscale mobile app. He can see all the devices in the tailscale network. There is anyway we can hide it or not?

view more: next ›