You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since CREATE CREDENTIAL is deprecated, and the new project type outputs .usqldbpack to be run with PackageDeploymentTool.exe, how do we handle external SQL database sources and credentials?
Database don't exists yet, so can't run. PowerShell to create credential on it.
Previously I handled this by running a PowerShell script that made the DB and schema, then ran PS to create credential, and then continued to create the rest of the analytics db.
Any suggestions? Should credentials instead be placed on master?
The text was updated successfully, but these errors were encountered:
Since CREATE CREDENTIAL is deprecated, and the new project type outputs .usqldbpack to be run with PackageDeploymentTool.exe, how do we handle external SQL database sources and credentials?
Database don't exists yet, so can't run. PowerShell to create credential on it.
Previously I handled this by running a PowerShell script that made the DB and schema, then ran PS to create credential, and then continued to create the rest of the analytics db.
Any suggestions? Should credentials instead be placed on master?
The text was updated successfully, but these errors were encountered: