Preguntas frecuentes

Once, and it is one trip to your browser. Choose I'm new, give a name and an email address, say whether it is for personal use or for work, and follow the link we email you. You are signed in, offered an optional password, and handed back to the app. After that it works offline indefinitely, and that installation is never asked again, whatever goes wrong later. A machine with no route to the internet skips the sign-in and uses a signed license file instead.

Never to register, and not for the work trial: confirm an email address and you are in. Subscribing to Pro or Enterprise asks for one. If you subscribe to Pro without having used the work trial, the 30-day trial that comes with it asks for a card so the subscription can continue afterwards, but nothing is charged until the trial ends and you can cancel first.

SQL Multicast checks for a new version when it starts, downloads it in the background and applies it the next time you launch. The release notes say what changed in each version.

In %APPDATA%\SqlMulticast\logs\. Settings has a button that opens the folder. Turn on Verbose logging before you reproduce a problem, and turn it off afterwards.

That depends on what the work is for. Personal projects, hobbies, learning and open source can use Community (free). Anything you do for an employer, a client or a business, of any size, needs Pro, up to 25 seats in one organization. Enterprise is for organizations that need more than 25 seats or the controls and paperwork a company needs, with a minimum of 10 seats. One DBA working alone inside a large company needs Pro, not Enterprise. The pricing page has the details, and the licensing docs say it in plain English.

Choose "my job, my employer or my clients" when you register. When you confirm your email you get a Pro license with no limits for 30 days, with no card asked for. When it ends your license returns to Community and everything you built is still there; subscribe to keep using it for work. It is once per organization. Enterprise has no self-service trial, but an organization that tells us it needs Enterprise gets the same 30 days while we talk.

Signed in, open your account page and choose Manage billing or cancel subscription. If you cannot sign in, or would rather not, use the billing portal: enter the email address you subscribed with, and you are sent a one-time code. From there you can download invoices and receipts, change your card, and cancel.

Nothing you built goes away. Workspaces, projects, scripts, distribution lists and run history are all still there, and the app keeps running. You fall back to the Community tier's limits: 5 connections and 25 databases per run. Nothing is deleted and nothing is held hostage.

The app keeps working at the Community tier's limits. A license service that cannot be reached, a lease that expired while the machine was offline, a corrupt cached license file and a revoked sign-in all reduce what the app will do, and none of them locks you out. The License and account window in the app tells you which one it is, and it works with no network at all.

Yes. Enterprise licenses are issued as a signed file that verifies entirely offline, with no call home. It is not tied to a machine, so one file works across a fleet, and it works on a CI agent that has nobody to sign in. See the licensing docs for how to apply it.

No. The formatter, coverage reporting, the sqlmc command line and the MCP server are in every tier and stay there. Automation is not a paid feature.

Your name, email address and organization when you register. The app can optionally report an anonymous install count, which is disclosed on first run, has a visible off switch, and never includes server names, connection strings or script content. Read the privacy policy for the full account.

Saved passwords are scoped to your Windows user account on that machine. A cloned workspace brings the connections but never the credentials, so enter each password again. Ticking Save password stores it locally.

Containers and lab servers usually need Trust server certificate switched on for the connection. Do not switch it on for a server whose certificate should be valid, because that turns off the check that would tell you it is not.

That is drift: the databases are not identical. Run a coverage scan against the target group to see how widespread it is before you write the fix. The documentation covers it under schema coverage.

This is almost always a variable that is not set for the selected environment, which substitutes as NULL. Check the Variables tab in the results pane to see what actually resolved, and look for a blank cell in the selected environment's column in the variable editor.

If you have an account, open a ticket: you can follow the conversation on the site and we email you when we reply. If you do not, use the contact form and we will reply by email. Please include your version of SQL Multicast and, for a licensing question, the reference shown under License and account in the app, because that is how we find the matching record. Check the known issues first, in case there is already a workaround.

Sign in and open My tickets. Each ticket shows the whole conversation and whose turn it is: Waiting for us means we owe you a reply, and Waiting for you means we are expecting yours. You can reply, or close a ticket once it is solved, and replying to a closed ticket reopens it. Messages sent through the contact form without an account are answered by email and do not appear there.

Email security@sqlmulticast.com, not the contact form. Please give us a reasonable chance to fix it before publishing, and we will credit you if you would like.