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
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 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.
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 3 years ago.
Improve this question
I have few tables that I have to sync between 3 different RDBMS systems (PostgreSQL databases, a SQL Server and a Firebird Database).
Currently I simply connect to my Firebird database and pull the few relevant tables to my PostgreSQL database, but as databases change, new tables require querying and with the addition of a SQL Server database to the mix I feel this solution is ill fitting.
I've done some research on BI tools , but I still need to query data from this data source and show them inside a Windows Forms application.
PS: it's not a migration and I only need to query the data from these "satellite" databases
Using PostgreSQL as your hub, you can use Foreign Data Wrappers to reach out to the other two databases whenever a query wants their data. Then it will always be up to date, but performance might suffer compared to actually importing the data. For reaching SQL Server, you can use tds_fdw, and for firebird you can use firebird_fdw. I have never used either one of these, so this is just a starting point.
You could probably pick SQL Server as your hub and accomplish the same thing, it calls them "linked servers" rather than Foreign Data Wrappers, see for example.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
We have the need to sync an Azure SQL Database (PaaS) with a SQL Server on-premises instance (on customer’s DataCenter), as both are being fed with data from different systems. Both databases share the same schema, and we need the sync process to be bidirectional, where every 5 minutes the data from the Azure SQL Database goes down and every hour the data from the SQL Server (Standard) instance goes up.
We thought of using SQL Data Sync (https://learn.microsoft.com/en-us/azure/sql-database/sql-database-get-started-sql-data-sync), as its the most straightforward solution to achieve what we want, were almost no configuration or custom code is needed. The main problem is that it’s still on Preview, and it has been like that for some years. So, my questions are:
1) Why is it still on preview?
2) What other alternatives would you consider for this requirement, without losing transparency and performance?
PS: There's a similar question form almost 3 years ago (Is SQL Azure Data Sync Production Ready?)
It will be GA this month.
SSIS could be another solution but it requires certain domain knowledge and effort to create an maintain the solution.
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 6 years ago.
Improve this question
I have to design website to start migration of sql server from one version to another and based on client database requirements we will tell him the cost of this migration and which sql server version is best to use?
There are some important factors in choosing SQL Server version and edition on following topics:
How many CPU cores it can utilize
How much RAM it can utilize
What key feature it supports. for instance some versions do not support columnstore index or partitioning. Read the feature list.
Number/Size of supported databases
AFAIK some editions have better query optimization. (I'm not sure though)
Do you need BI feature? How about Replication, High Availability features like Mirroring? Always On? Data Encryption? Data/Index Compression?
You need to know, volume of data and concurrent users to decide.
Some features are critical for large volume databases and some are not.
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.