This has happened to me on two different machines. When I run SSMS I am unable to create a database. I've seen other posts about giving users permissions, but it seems like a catch 22 because I don't have rights to give other users permissions. I know there were posts about a Surface Area Configuration Tool, but I don't see that with SS 2008. Is this possibly an installation issue?
Related
Specifically for my connection to an Azure SQL Server Database after upgrading to Azure Data Studio v1.41.
When I connect into my Server/Database, and expand the Tables section from the left side menu, none of my tables appear. (Also my Views and Stored Procedures are not visible.)
They do still exist. They appear when the Manage option is selected, and I can access the data.
This means I am without access to Table Design for existing tables and other quick actions that would appear there.
Please help, it was all there when I had v1.40 installed earlier!
I have tried to log in using different accounts (server admin, Azure AD and another user account), none of which showed the tables under server connection. I have also restarted, refreshed and tried the Insider v1.42 build, all with the same outcome.
This has been fixed in the latest release of Azure Data Studio 1.41.1:
Bug fixes in 1.41.1
New Item
Details
Connection
Fixed a bug causing incorrect Azure account tenant selection when connecting to server through the Azure view.
Object Explorer
Fixed a regression which caused Object Explorer to not show database objects for Azure SQL DB Basic SLO.
I can confirmed, as well, that the regression no longer occurs:
There are a ton of threads about this error, but I can't find an answer for what I'm dealing with. I have a simple view in DB1 and a user that has permission to select from it. It's not a cross database script. Just a simple SELECT from DB1 only. The server has recently been migrated to 2016 (from 2008) by a vendor and everything was working fine until recently when I would get this error sporadically, but about not having access to DB2. That user is not looking at DB2 at all and again, no cross-database SELECT. This now has also happened to another user. I just can't figure this out. Any ideas?
Thanks!
I would like to ask your help to re-sync old AD user (let's say AD\username) with new AD user (AD\username - the same name but different SIDs) in SQL Server 2008 R2.
I looked at the question "SQL Server Windows Login - Same Name Different User (SID)" but in my case the old user owns schema and tables in multiple DBs and cannot DROP the old username.
Can anyone help, please?
Thank you in advance
CI
You can use a few methods:
sp_help_revlogin was created for SQL Server 2005 and is still used quite often. This support article explains it in-depth and shows how to use it.
dbatools.io is an open source community tool suite created in PowerShell by some very generous folks. There are a few blogs showing how to use their scripts, but here is one to handle the logins.
Find other scripts which do the same thing, like this one which is for AGs but still applies.
I created a few databases within a large hosting provider network. When I use Microsoft SQL Server Management Studio 2008 R2 to connect to the SQL instance I see a list of every SQL database on the server. Is there a way I can tell Management Studio to only display the tables I have access to?
I found a few articles online that said to deny my user the permission to view the other databases. That wouldn't be an issue, except I don't think I can do that from my end. I'd like to solve my problem without having to call my hosting provider. Regards.
Unfortunately what you are asking is NOT possible at this time. I know this is NOT what you are looking for :-)
I have backed up and restored a MS SQL Server 2005 database to a new server.
What is the best way of recreating the login, the users, and the user permissions?
On SQL Server 2000's Enterprise Manager I was able to script the logins, script the users and script the user permissions all seperately. I could then run one after the other and the only remaining manual step was to set the login password (which do not script for security reasons)
This does not seem possible in SQL Server 2005's Management Studio, making everything very fiddly and time consuming. (I end up having to script the whole database, delete all logins and users from the new database, run the script, and then trawl through a mixture of error message to see what worked and what didn't.)
Does anyone have any experience and recommendations on this?
The easiest way to do this is with Microsoft's sp_help_revlogin, a stored procedure that scripts all SQL Server logins, defaults and passwords, and keeps the same SIDs.
You can find it in this knowledge base article:
http://support.microsoft.com/kb/918992
Run this:
EXEC sp_change_users_login 'Report'
This will show a list of all Orphaned users, for example:
Now execute this script here for each user, for example
exec sp_change_users_login 'Update_One', 'UserNameExample', 'UserNameExample'
This fixed my problem.
I use the SQL Compare product from Red Gate (http://www.red-gate.com/products/SQL_Compare/index.htm). There are other similar products around but I've had no reason to look for one as SQL Compare has never let me down.
You'll find it is useful for a lot more than the your current requirement as it will help synchronize all types of database object, not just login and permissions.