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 2 years ago.
Improve this question
I'm new to the topic of databases and DBMS.
I have written the PhoneBook program with C# .NET and SQL Server.
My question is how can I run this program on a users computer who hasn't got SQL Server?
I want when they click on the execution file on their computer, it will work immediately and correctly and they can store new users or delete some user
You could host a SQL server for your users and require they have an internet connection.
You could rewrite it as a web application, also requiring an internet connection.
Or you can use SQLite, an embedded SQL client and, for lack of a better term, server. That's what I'd recommend, and that's what many applications do. SQLite is not fully compatible with SQL Server, so you'd have to rewrite some of your SQL.
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 2 years ago.
Improve this question
I'm hoping for some opinions on the best options for how to replicate, in real time, data from a production SQL Server database onto another SQL instance. This second instance would be for vendors who need to access some of the tables from the production database, but we would prefer that they not directly access our production instance.
I have some awareness of transactional replication and log shipping as possible solutions, but I would be interested in pros/cons of these approaches, or superior alternative solutions you may have tried.
I realize there are many topics already on Stack Overflow that discuss how to do this, but many that I found were older (technology's always changing), or focused on a very specific scenario.
For read-only access you can use AlwaysOn Availability Group feature introduced with SQL Server 2012
Documentation:
https://learn.microsoft.com/en-gb/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server?view=sql-server-ver15
https://learn.microsoft.com/en-gb/sql/database-engine/availability-groups/windows/configure-replication-for-always-on-availability-groups-sql-server?view=sql-server-ver15
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 is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am new to sql server, Which method is best to work with sql server COMMAND LINE OR GUI.
What do you mean "work with"?
I would say that that Microsoft SQL Management Studio, should be more than sufficient for anything you want to do. Using this should almost make any task relatively simpler than using CLI.
For regular usage, I use the GUI interface. It has access to everything I need to do within one or two clicks. For automation tasks, or to interact with the service when the GUI is hanging, I use the command line.
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