Comments
Sort by recent activity
You can, but if you perform other In-Memory OLTP DDL, you'll get the error again. This is a bit of an effect of the way DLM Dashboard uses DDL triggers. / comments
You can, but if you perform other In-Memory OLTP DDL, you'll get the error again. This is a bit of an effect of the way DLM Dashboard uses DDL triggers.
I've got the file (BTW, upload as ZIP should work). The options are dramatically different as I look through them. I don't know that I can get a mapping from options such as 1 to Upper Case for the enums in the old styles today, but I've left a few messages with development to try and sort this out. When I look through your style, I can't quite tell what items to map across.
I'll update as soon as I can. / comments
I've got the file (BTW, upload as ZIP should work). The options are dramatically different as I look through them. I don't know that I can get a mapping from options such as 1 to Upper Case for the...
OK, I found a converter tool. Please try this style and let me know if it works. / comments
OK, I found a converter tool. Please try this style and let me know if it works.
Can you upload the file for someone to examine? / comments
Can you upload the file for someone to examine?
Confirmed this as an issue with Prompt 8.2.2.x / comments
Confirmed this as an issue with Prompt 8.2.2.x
Is this the same object or all objects or a type of object (all procs)? I haven't seen this, but sometimes the Compare engine will find an inconsistent state that it can't resolve.
SQL Source Control essentially manages a SQL Compare execution between your database and your VCS. Did the object get changed in the VCS outside of SSMS/SQL Source Control? / comments
Is this the same object or all objects or a type of object (all procs)? I haven't seen this, but sometimes the Compare engine will find an inconsistent state that it can't resolve.
SQL Source Contr...
Can you upload the schema for the source? Maybe script out and rename anything that might be NDA. It would be good to test this. Also, which Compare version? / comments
Can you upload the schema for the source? Maybe script out and rename anything that might be NDA. It would be good to test this. Also, which Compare version?
I do this regularly and it works great. If you need help or more information, please ask. This all comes down to the VSTS agent acting as the client that deploys. Or you having a task that has the required credentials for the VSTS agent to make a connection. / comments
I do this regularly and it works great. If you need help or more information, please ask. This all comes down to the VSTS agent acting as the client that deploys. Or you having a task that has the ...
Please post the code that creates this. Or is this in the SQL Server error log? If that's the case, this isn't the correct place for the question. This is a forum for SQL Prompt questions/issues.
If you need general SQL Server help, please post a question at www.sqlservercentral.com/forums in the forum for your version. / comments
Please post the code that creates this. Or is this in the SQL Server error log? If that's the case, this isn't the correct place for the question. This is a forum for SQL Prompt questions/issues.
I...
First, this works and I demo this regularly. The key is your agent. How have you configured your process?
For me, I use SQL Auth, and I set a user name and password as variables for the environment. I use a secret for the password. Alternatively, you could run your agent as an account that has access, but I tend to find this less secure, unless I were to set a different pipeline for this release, using a specific agent account that I can limit to sysadmins accessing for release. I would be wary of the same pipeline/agent for build and release. Two separate functions.
Here's my production release definition: [image]
For my production side, I have a variable here: [image]
The VSTS agent is functioning exactly as if it were logged in as you. You need to set security context and networking to be sure the agent can connect to your instance. After that, it's running DDL/DML, just as any other login/user. The rights/permissions depend on what you allow to happen. If a db needs to be created, then you need those rights. If it's just CREATE/ALTER/DROP objects, those rights are needed. / comments
First, this works and I demo this regularly. The key is your agent. How have you configured your process?
For me, I use SQL Auth, and I set a user name and password as variables for the environment...