Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
In my work I have a BAK file (which I'm working on in SSMS) and the system Admin gave me permissions via my Active directory .
NOw ,
If I'm taking the bak to another place (e.g. home), and I'm adding the sa user (which is me, and I don't have Server Environment in my house) as full controller.
Should I be able to have full control over it (at home )?
If you have a backup file with no encryption, then you can restore it on your local machine as sa. When you do this, though, the database users will be orphaned, and you will have to modify that. No big deal, and as an sa you'll already be mapped to the dbo user, but if you have an application hitting the database using a different database login/user then that will be an issue.
As long as you are administrator on your machine at home you should have full control. The only items you may not be able to get to is if certain columns are encrypted.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to know when an application is pointing to a database, how to make sure that it is the correct database.
Can you let me know this from a Developer, DBA and a tester perspectives?
is it the database connection string? or update date on tables entries? any database scripts related check?
Thank you all in advance.
From a developer perspective, checking the connection string is the typical way to tell which database an application is pointing to. Of course, the big thing to look out for with this is making sure that you're looking at the right connection string, especially if you are using more than one of them in that application.
Depending on your application, you should be able to print a debugging message near your code that initializes the connection to the database that prints out the connection string that is being used for that connection. This could also allow the tester to know which database is being accessed.
From a DBA perspective, profiling the server could show active connections and/or queries with various amounts of detail depending on the database server being used.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have my local database called CBS and on the production server there is the same database. Sometimes I want to make a backup on production and want to restore it on my local machine. With SQL Server 2008 I had no problems but now I can't do that.
To restore the production database I changed the destination database from CBS to CBS_PROD. I also changed the file names of the destination database. After restore the CBS_PROD is OK but my former local CBS database is in state "Restoring...".
Please help.
Thanks
Andi
Try Executing this statement
RESTORE DATABASE DataBase_Name
WITH RECOVERY
GO
If you are using SSMS to restore the database make sure you select the following option in "Recovery State" Section.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
A user entered a ticket for an OLD Access database and form project that they use daily. They are saying that the database cannot be found when they use it. I haven't used MS Access to design a database or interface since college so I have no idea where to find the database it's trying access.
I want to try and locate the DB to see if 1) it exists and 2) is not corrupt
The main interface is done through a *.adp file. Where is the connection string information stored in the file?
Ive opened it in MS Access 2007.
With an ADP, SQL Server is used for all data storage.
In the Immediate window (go there with Ctrl+g), inspect the ConnectionString and Provider properties:
? CurrentProject.Connection.ConnectionString
? CurrentProject.Connection.Provider
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
So I have a shared hosting for ASP.NET MVC3 and I just created a new database on Plesk.
Next I wanted to connect to database remotely using Sql Manager and I entered server name, username and password.
Everything fine so far but after I clicked on Database Name, it gave me a list of all sort of databases I never heard of.I guess those are databases of other people.
I am wondering is this normal behavior?
The permissions to hide database you don't have permissions in have side effects
So you can usually see the databases but you should have no rights at all to see any data in them, even system data. That is, there should be no login-user mapping
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
SSMS (SQL Server Management Studio) has saved 3 login information on my computer. However, when I tell it to remeber the 4th login info, it simply won't remember anything next time.
This means that each and every time I want to connect using that Login, I should provide user name and password, and this really sucks.
Do you know how can we manage saved login information of the login Dialog?
I filed a bug about this issue, that we can't manage that MRU list:
SSMS : Expose "Connect to Server" MRU list to users
They've fixed the issue where you had to either deal with the list you have or purge the entire thing by deleting mru.dat or SqlStudio.bin. But they haven't really made the list any more manageable. I've asked the author of a popular free add-in about extending his tool to support this functionality and he's potentially going to look into it.
In the meantime, if you really want to have many (most complain about the opposite, too many redundant entries in the list), you should just create four different registered servers, and connect to them from the Registered Servers node in Management Studio. This is much easier than trying to identify which 127.0.0.1 credentials you want to connect to - much easier to name your registered servers 127.0.0.1/login-name for much quicker recognition.
If you want to be able to identify a server and login by server name alone, then maybe you could add entries to your hosts files that all point to 127.0.0.1, but look like 'local.login1' and 'local.login2'... you should be able to save each of these connection entries separately because Management Studio will treat them all as different servers, even if they ultimately point to the same instance of SQL Server.