How to use dbdeploy with SQL Server? - mysql

I need help in setting up dbdeploy for my SQL Server database and MySQL Server.
The example in the dbdeploy website does not tell me how to set the drivers for SQL Server and MySQL. Am a bit lost.
Sample scripts will be appreciated.
Thanks

As part of some ReadyRoll market research we commissioned a poll in the Simple Talk newsletter which revealed that DBUp is now the most adopted database migrations tool after EF migrations, so it would be worth considering this solution as an alternative to DBDeploy.
(Simple Talk's audience is primarily people who use the .NET/SQL Server stack)
Disclaimer: I work for Redgate and the research described above was focused on understanding how ReadyRoll could provide additional value on existing OSS migrations-based solutions.

I tried to use dbdeploy for my project with MSSQL 2008
But I didn't like it and now for MS SQL we use Agile DBRIRE

Related

Auditing a .net application using sql

What would be the answer for how do you audit .net application for security using Sql server database?
I said by using triggers. But I don’t know the answer. Please help.
This may help you just have a look at [SQLShack page] (https://www.sqlshack.com/various-techniques-to-audit-sql-server-databases/)
They list out and explain some of the auditing techniques using SQL server databases.

Data transfer between online Mysql and SQL Server databases

I want to transfer data between Mysql and SQL Server databases, but both are hosted online.
I tried to do this thing using odbc, but it did not work. What is the best solution for this task? ODBC/web services/some other method? Please help me to solve this problem.
You could take a look at the Microsoft Sync Framework, it's very flexible and can deal with different databases.
http://msdn.microsoft.com/en-us/sync/default
There are some database syncing tools already existed. One great tool I can recommend is the Navicat Premium. This tool supports different servers.
Create your own data sync app. It's not so hard to create.

MySQL on remote box & Microsoft Entity Framework tips?

We have a client with a MySQL database that we need to access over the internet. A port number is open on their end for us to gain access and run queries.
I was wondering if anyone's had experience using the Entity Framework with a MySQL database over the internet and what gotchas and tips you had to share? Is it pretty straightforward getting to the data in your experience? We'll likely be using the most recent version of EF, if that makes a difference. Thanks much for sharing.
Just mentioned this over here
would this be of interest WCF Data Services

Using LINQ with databases other than SQL Server Express 2005

I'm just starting to look into using LINQ for my database (and XML, and data object!) needs, but need to decide on which database to go with. I've been reading Pro LINQ, and it says that currently, LINQ in .NET 3.5 only supports SQL Server. I have done some googling, and have found references to using LINQ with MySQL and PostgreSQL (my other two DB options), but they are refer to DLinq, which I understand to be the predecessor of LINQ to DB.
I've read interesting and informative comparisons of the three databases here and here, but am still torn. I do not have any in-depth database experience, so it's important to be able to get the software installed and configured easily, or at least be easy to figure out how to compile a list of steps to configure it. I definitely want to have transactional support as well. But most importantly -- I want to use LINQ.
I'd like to hear what everyone here is using, whether it's SQL Server because LINQ supports it natively, or the other two with some additional component for LINQ support that I haven't yet found.
We use devart's dotConnect provider for Linq-to-Oracle and have been very pleased. They try and make the functionality match Linq-to-SQL as close as possible, which seems to be what you're looking for.
They have providers for:
Oracle
MySQL
PostgreSQL
SQLite
SQL Server
From a cost perspective, it's an excellent deal I'd say, just pay for developer seats, no server licensing.

New Project : MySQL or SQL 2005 Express

I am starting a new client/server project at work and I want to start using some of the newer technologies I've been reading about, LINQ and Generics being the main ones. Up until now I have been developing these types of applications with MySQL as clients were unwilling to pay the large licence costs for MSSQL.
I have played around a small amount with the express versions but have never actually developed anything with them. The new application will not have more than 5 concurrent connections but will be needed for daily reporting.
Can MSSQL 2005 express still be downloaded? I cant seem to find it on the microsoft site. I would be hesitant to use MSSQL 2008 on a project so soon after its release.
Are the express version adequate for my needs, I'm sure loads of people reading this have used them. Did you encounter any problems?
The answer to the question on any project in regards to what platform/technologies to use is: What does everyone know best?
Yes express can still be downloaded.
Will it fit your requirements? That depends on your requirements, of course. I have deployed MSSQL2005 Express on several enterprise level projects which I knew had a fixed database size that would never be exceeded (Express has a limit of each database of 4Gb). Also keep in mind there are other hardware constraints such as a 1 cpu limit.
Another thing to consider is if you need the Enterprise level tools that come with a paid edition of SQL Server. If you are moving a lot of flat data around you are stuck writing your own Bulk Copy Procs, which rule the house, but its an extra step, no doubt.
Note sure about #2 but you can download SQL Server Express 2005 here.
Sql express has more features, and is a lot more powerful, but will only run on windows boxes. If you ever need to scale Sql express can be switched easily to a commercial variant.
MySql doesn't support half the features, but does have most of the basic ones you actually need, and will run on windows or *nix boxes. It's also not throttled in the same way as Sql express is.
In my opinion (having used both extensively, but not touched MySql for a few years) Sql express is a far better DB system. If you're building .Net applications the Linq support is a deal clincher.
If you aren't going for pure Sql server support, I wouldn't go for pure MySql support instead. Use a DBFactory design pattern to load your data layer or use simple SQL:92 syntax that's a lowest common denominator.
Why not go to Sql server express 2008?
I'm mostly going to advocate MS SQL Server because of .NET integration. Linq To Sql is pretty much my favorite way to do deal with databases these days: anonymous functions make everything better! My current place of work has also used MSSQL Express for real projects, so you have at least two of us confirming that the restrictions aren't too harsh.
I have about 50 web sites running perl/apache/mysql and about 10 running C#/ASP.Net/SQL Server (Lite) and other (large) applications running on SQL Server (Heavy). I never have problems with SQL Server - it just works. I often have problems with MySQL.
My advice would be to go for the SQL Server based option even if you had to pay for it.