I have configured Bonobo GIT and it's working fine with SQL Lite.
Can we user SQL Server with Bonobo GIT? If, Yes then where can I find the ready made database?
You can run it with SQL Server, and it will create the database for you, but personally (as someone who's done some work on Bonobo) I wouldn't recommend it - the database tends to be very small anyway, and you'll get no significant advantage from using SQL Server.
Related
I have two remote databases, Oracle 19c and SQL Server 19. In my redhat linux, I have to read SQL Server table and write it to Oracle.
I wrote a Python code to read data from SQL Server and insert it to Oracle database. But, I think it is so slow. Since, the table has about 16 million records.
I search a lot and see this post:
https://stackoverflow.com/a/66550879/6640504
It said that Oracle Transparent Gateway makes it possible to run a procedure for migrating data from extra database to Oracle in little time.
I can access to Oracle database using terminal and don't have any graphical accesses.
Would you please guide me if Oracle Transparent Gateway is the best way to migrate data from SQL Server to Oracle database, how to install Oracle Transparent Gateway and use it? If not, what is the best way?
Any help is really appreciated.
One solution would be to work from SQL Developer.
You can download SQL Developer for free from https://www.oracle.com/tools/downloads/sqldev-downloads.html
SQL Developer provides a "migration workbench" that supports SQL Server.
The data migration can be done online or offline.
Online causes the table data to be moved by SQL Developer when you have completed the necessary information in the wizard; Offline causes SQL Developer to generate scripts after you have completed the necessary information in the wizard, and you must later run those scripts if you want to move the data. (Online moves are convenient for moving small data sets; offline moves are useful for moving large volumes of data.)
I downloaded the Bonobo Git Server and installed it both locally (Windows 7) and on a Server (Windows 2012). I initially used the default setup, to learn about it. The default username and password worked, as did creating test users.
I then removed all instances of SQLite and swapped them to SQL Server. At the same time, I also enabled Windows Authentication with AD Member Services. After creating a new catalog, bonobogit, on a SQL Server instance I can see tables related to Repos, Teams, Users, and Roles were created. However, none of these appear to be used. Instead, there appears to be corresponding directories and files under the ~/App_Data directory.
What is the purpose of SQL Server or SQLite for a Bonobo Git server? Is it possible the combination of settings I have make them moot?
Thank you in advance for any guidance or advice.
What is the purpose of SQL Server or SQLite for a Bonobo Git server?
The sql server is used to store all your data like stash does.
Git itself doesn't require but usually remote server use it for several reasons:
Backups - Store the data in Db as well for backups
User management
Clustering
Performance
and more.
Basically its much faster to read data from database then from HD, the lookup is much faster, backup are easier, recovery and sociability again are much easier to maintenance.
We have migrated our production environment to Azure (using SQL Azure instead of SQL Server)
Our local development environment uses SQL Server. We write change scripts when database changes need to occur during a release.
PROBLEM
The issue now is that some T-SQL commands/statements/keywords don't work when run on SQL Azure. This is constantly disrupting our release process.
Educating everyone to use a subset of T-SQL is happening, but these problems continue to crop up.
Is it not possible for us to parse our SQL scripts as 'Azure SQL compatible' in SQL Server using the parser before running them:
Thanks
If you use the new "SQL Server Database Project", there is a feature in Visual Studio that allows you to select the "Target Platform" to SQL Azure. This will allow you to build all your t-sql scripts and check them for SQL Azure compatibility. Any compatibility errors will throw errors and it can create a bacdac/dacpac/t-sql script that is compatible with SQL Azure.
In order to take advantage of this, you have to manage your code using the "SQL Server Database Project" projects in Visual Studio.
You are not going to like this answer .. but the best bet is to move your development environment to SQL Azure. We started in the same process but you will just have the constant battle. We used Redgates SQL Compare tools but I don't believe they will solve your problems, but maybe worth a shot as they are constantly getting better.
Even if you have multiple devs and they each need a SQL Database I would still recommend getting everyone to signed up with Azure and pay the cost under it. Thankfully the database are not that expensive to run, and you might get under the free tier structure. It is still cheaper for us to run the cost of the SQL Azure Dev boxes than it is to have the pain and waste of time at release.
hey guys,
i am creating a website for a client, my website is almost complete, now i want to upload the database to the clients production server, but i dont have any hint about how to upload the database to the production server. can anyone please help me with the steps how to upload the sql server 2008 database to the production server, keeping in mind, the production is not the dedicated server, i think i have to run my database script, on the server, but i dont know how to run, will i get the option for the same on the production server, or need to dig for the same on the sql server...
Please help me for this as soon as possible..
Thanks and Regards
Abbas Electricwala
I can think of few methods.
For example,
If you have version controlled database objects in Visual Studio then you can just deploy it to server by specifying production database connection. This MSDN link can help you in that case.
Or,
You can take backup of your current development database and restore it to production server. If you have never worked with backup and restore, read on these MSDN links, for Backup, for Restore. Of course, in normal situation Backup/Restore is not this straight forward but since your system is new and not in use, this should be easy task.
Or,
Script out database objects from current development server and run those scripts to production server (say by using Sql Server Management Studio). Generating scripts is easy but I don't think anyone can explain it step-by-step in few lines. But you can read this MSDN link for detailed information.
I am on a shared host and whilst in development (umbraco) I think it would be easier to use VistaDB then package up to install to SQL Server. However, I have already started using SQL Server. Is there a way to migrate my SQL Server (2008) database to VistaDB. I assume the schema is identical but I need a way/tool to move the data to VistaDB.
You could migrate to VistaDB in the same way that you want to migrate data from development to production. Create a package from your current SQL Server-based development site, then create a new empty install of Umbraco with a VistaDB database and import the package there.
This would also be a useful dry run to check that migration to production is going to work as smoothly as you expect.
You can also use the Data Migration Tool in VistaDB to migrate any SQL Server database to VistaDB 4. If you need an older migration (I think the current Umbraco is still using VDB3 files) contact support through the VistaDB.Net site and someone will help you.