New answers tagged

1

These are out of the box features of SQL Server so you'll essentially need to follow the Microsoft Books Online and other resources on setting them up. Replication has a lot of small steps and basic prerequisites but it's essentially a wizard, so it's rather simple if you just follow the documentation carefully. Here's some helpful references for setting up ...


0

I maybe found two solution for you: HIDE Hide Table "Person.Address" EXEC sp_addextendedproperty @name = N'microsoft_database_tools_support', @value = 'Hide', @level0type = N'Schema', @level0name = 'Person', @level1type = N'Table', @level1name = 'Address'; GO Show Table "Person.Address" EXEC sp_dropextendedproperty @name = N'...


1

You shouldn't have to explicitly DENY any of those permissions since SQL Server is implicitly deny-first, meaning a Login / User / Security Principal (such as a Role) has no access to anything until you've explicitly granted access (either via scripting it with T-SQL using the GRANT keyword or using the UI that SSMS provides). Explicitly denying a permission ...


2

You will not be able to turn on Trace Flag 4199 in Azure SQL Server. You will get an error message. In fact, you cannot turn on any trace flags (globally or session scope) in the Azure SQL database. At the time of writing this, there were 24 trace flags enabled with Global Scope for Azure SQL database. You can check the list by running DBCC TRACESTATUS.If ...


1

SSMS should display this warning when you delete the login: Deleting server logins does not delete the database users associated with the logins. To complete the process, delete the users in each database. It may be necessary to first transfer the ownership of schemas to new users. And so in the master database don't run DROP LOGIN <username> . The ...


1

There's two concepts with security at play here, and in general how SQL Server works. There are Logins and Users, which the differences are discussed a little further in this StackOverflow answer. You've deleted the Logins which is server level, but the Users associated to those Logins still exist at the database level, which has its own Security node you ...


0

This is a screenshot of Azure SQL Analytics. You set up a Log Analytics Workspace and attach your databases to it. Note it takes a few minutes for them to show up but you can then see timeouts. It's still in preview and definitely a bit klunky, but I'm hoping to get some useful information from it. One thing to note is if you drill down to a query that ...


1

Each leaf node row in a SQL Server b-tree index uniquely identifies a single row in the table by a unique key. In a non-clustered index, this unique key consists of the declared key columns plus the row locator. The row locator is the clustered index key (including uniqueifier for when the CI key value is not unique). With a heap (no clustered index on the ...


0

I found this solution: https://www.youtube.com/watch?v=7QI1VjbS0YI&t=460s&ab_channel=RajasekharReddyBolla In case you need to migrate with zero downtime from Azure VM to Azure SQL Database


0

Nice question, I had the same scenario: Transactional Replication from on-prem to Azure SQL Database. My solution was: Replication > Local Publication > Right click on your publication > Properties > Agent Security > Security Settings... and here setup your local Windows account and impersonate the same


0

We are using elastic pools and as well as MBuschi´s comments the 2 biggest factors that drive our decision on whether to use a new pool are Storage - if you hit the max storage per pool limit stuff will stop working & this is bad Region - pick an Azure region that is close to your customers - they will get faster response time & thank you for it ...


0

It seems that you are below the limits in both cases, so it seems pretty the same. These are the limits: As you can see, the only thing that really seems to matter in your case and that donsen't double when you switch from 100edtu to 200edtu, is the max concurrent sessions. So, if you are far below this limit, I suggest you to choose basing on the easiest ...


1

Azure Synapse Pathway is a new tool currently in preview which can look at existing Netezza code for you, attempt to convert it and flag up errors. Download the tool and run it against your Netezza installation. Start here: https://docs.microsoft.com/en-us/sql/tools/synapse-pathway/azure-synapse-pathway-overview?view=azure-sqldw-latest As a wizard, it's ...


Top 50 recent answers are included