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'm currently using SQL Server 2008 R2 Change Tracking (not Change Data Capture) and SSIS to extract incremental changes from several source databases.
Until now, I'd been using restored backups to do this so I didn't need to worry about Snapshot Isolation. However, I now need to point these packages at the production databases.
I know that setting the Snapshot Isolation Level on for the tracked databases is recommended to ensure consistency of the ETL extracts. I'm reluctant to do this because of possible degradation in performance.
Since I'm extracting late at night, is there some reason I can't use the following process?
Create a database snapshot for temporary use.
Get the Change Tracking Current Version of the Production Database.
Compare it with the previous successful run version.
Extract from the Database Snapshot instead of the Production Database.
After successful load, drop the Database Snapshot.
We're using 2008 R2 Enterprise Edition. is there any downside to this? Am I missing something?
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 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 3 years ago.
Improve this question
Our DBA recently introduce the whole idea of DB Project for maintaining sql (DDL and DML) check in part however I feel like it's of no benefit at all. Is anyone knows any benefit of using DB project ? I would like to know real benefit.
Is anyone knows any benefit of using DB project ?
1) It tracks the change history of your database schema, and stores your schema in a version control system.
2) It integrates with your DevOps workflow, and enables you to track what version of your schema is deployed in what environment.
3) Manages the creation of DDL change scripts for upgrading a target environment to a specific version of the schema.
4) Prevents Schema Drift in environments by detecting and fixing changes made directly in environments.
An easy way to get started with database projects is to continue with your connected database development workflow, and use the Schema Compare tool to update your Database Project and check it in to source control.
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 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 am pretty new to SSIS and SQL in general, and I am still learning the ropes. I am trying to create a few integration packages. First step would be to retrieve the data from one database and load it into another. I've been using the data flow task for this ... However the next step would be to run this package once a daily at a given X time (eg. 1 am). The landing database would be continuously updated , just like the source.
On a seperate package, I'm looking for a way to copy the data from my landing database, and dump it all into another table. This needs to be done so that the package automatically retrieves the rows from the landing database, before it gets overwritten everyday.
Any suggestions?
Thanks!
Regarding the scheduling of both the created SSIS packages they can be scheduled as SQL Agent job. SQL Agent is part of all SQL Server Editions except Express Edition. For details how to create the automated job to load SSIS packages, please refer to Schedule SSIS
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
I have an input page in my C# application whereby my boss can enter sales info.
This page also has a clear button, which clears the contents of the table in the database. This clear button was convenient for testing, however now in hindsight a mistake.
All the records in the table have been deleted. There are no backups either.
Long shot, but is there any way of recovering this data using only SQL Server 2008?
If you still have the transaction logs, there are some tools, but these will cost some ...
See
How to undo a delete operation in SQL Server 2005?
and
https://web.archive.org/web/20080215075500/http://sqlserver2000.databases.aspfaq.com/how-do-i-recover-data-from-sql-server-s-log-files.html
Edit : Looks like Redgate is SQL 2000 only. Which leaves Apex. And if your clear function uses TRUNCATE, you are up the creek.
Edit:( 2008 support)
SQL Data Compare Professional
This version of SQL Data Compare, you can compare a live database with or against backup files and synchronize data and deleted tables with their data contents from the backup file or backup file set to the live database.
Redgate even say this should do the same job, and that is why they have not come with any new version.
Will probably need a backup or transaction log ....
See this subject.