I have ubuntu server running and CVS is installed on it. I'll be managing CVS with the Webmin gui tool. I'm migrating the server to the new ubuntu edition. I could easily migrate the CVS repository to the new machine but how could I migrate/export CVS Users?. Anybody has any idea?
First migrate the users(Unix or ldap) or create the users with the same names providing password for each , then move the CVS repositories to the new machine.
Related
I have a DB project which relies on SQL Server Database tools. I am trying to work on it on a Mac. The rest of the project is in .NET Core so that all works well. The database project throws an error on dotnet restore
/Users/mborozdin/src/ethos/FileRepository/src/FileRepository.Database/FileRepository.Database.sqlproj(63,3): error MSB4019: The imported project "/usr/local/share/dotnet/sdk/2.1.4/Microsoft/VisualStudio/v10.0/SSDT/Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Is there an alternative to SSDT which seems to be only available on Windows?
When you develop on the Mac,
You will put your SQL Server on the docker or Virtual Machine.
In other to connect, You need SQL Operations Studio for the Mac
Download Link
Is there an alternative to SSDT which seems to be only available on Windows?
The alternative is Azure Data Studio. As for:
SQL Database Projects extension
The SQL Database Projects extension brings project-based database development, well-known in SQL Server Data Tools (SSDT), to the cross-platform Azure Data Studio experience. From this early insiders release you can create, build, and publish a project from scratch or an existing database.
https://github.com/microsoft/azuredatastudio/issues/11105
I am trying to do dacpac deployment using SQLPackage on Linux.
My environment:
Server : Ubuntu Linux version 16.04
SQL Server 2017 latest release candidate version RC1.
SQL Server installation is successful and I am able to create tables on SQL Server database on Ubuntu. Now I am trying to implement dacpac deployment on Linux. As per this documentation
https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-export-import-with-sqlpackage
SQLPackage executable has to be at /opt/mssql/bin. But it is not. Any idea how to install SQLPackage on linux?
When I check the older version which is CTP 2.1 I have that SqlPackage executable. Is that missed in RC 1?
-Regarding temporary removal of sqlpackage from SQL Server 2017 package-
The goal is to offer customers the best CLI experience on Linux, macOS and Windows with a multi-os version of sqlpackage that uses DACFx APIs based on .NET Core.
As a stop-gap towards this goal, we offered an early preview version of the Windows-based sqlpackage in SQL2017 CTPs on Linux to seek customer feedback. We have removed this preview version of sqlpackage from SQL2017 RC1.
Work on the multi-os version of sqlpackage is in progress but I cannot share a release date at this time. Until then, you can use one or more of the alternatives below to import a dataset on each new run of your image:
1) restore an existing .bak file into the new image using the sqlcmd CLI tool.https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools
2) run sqlpackage on a Windows machine to work with SQL 2017 running in the new image.
3) generate a script with CREATE + INSERT statements for your database or specific tables. You can use SSMS’s Generate Script wizard on Windows or the new Python-based mssql-scripter CLI (public preview) to generate the script and check it into source control if you wish. Then, you can use the sqlcmd CLI tool to execute the script in your new image. For mssql-scripter installation instruction, please see README.md inhttps://github.com/Microsoft/sql-xplat-cli
Please send me an email at sanagama#microsoft.com if you have more questions or feedback and we'll be happy to help.
As mentioned by #Lin Leng-MSFT, sqlpackage has been removed from the installation package as of RC1. That said "SqlPackage can still be run against Linux remotely from Windows."
I am new to oracle database products. I am planning to install oracle 11g express edition in my PC,it looks like a standard installer.But in many of the oracle database installation tutorial mentions oracle universal installer.oracle universal installer provides more open options,but those options and features not available in downloaded oracle 11g express edition.
difference between two https://docs.oracle.com/cd/E17781_01/install.112/e18803/toc.htm#XEINW151 and http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r1/prod/install/dbinst/windbinst2.htm
so anyone explain me exactly what is oracle universal installer??Thx in advance.
As the name suggests oracle universal installer is a utility which can be used to install or uninstall multiple oracle products.
The utility can also check pre-requisites before installing a new software.
Only thing you need to do is to provide path to products.xml file inside oraparam.ini file. This can be location for the file on your physical machine or remote location may be hosted on oracle site.
The products.xml file actually have the information about the product being installed for example it is Oracle Client or DB.
For more information please check this link
FYI, this question would have been better asked on the DBA site since it has nothing to do with programming.
XE is a minimal installation for test/dev work so I guess they decided not to clutter it up with OUI, which I have never liked anyway. OUI is simply Oracle's Java-based installer that installs and keeps track of the majority of Oracle software you have installed on your system. There's nothing special about it, and you have no need to worry about missing out on something. If you were installing the standard database, it would try to start the network config tool that creates the TNSNames.ora file, for example. It's been a while since I used XE but I think it's install just creates a generic one for connecting to the XE instance.
I have an instance of plastic installed on my local machine version 5.0.44.519.
This instance is using SQL Server backend.
In here i have several repositories.
rep_1
rep_2
rep_6
now i have backed up these repositories with no problem.
the problem now is that when i go to restore the rep_ databases onto the other plastic instance on the development server i have problems.
the plastic installed on the dev server already had some repositories in it but thats ok, they are rep_24, rep_35 etc. etc. no conflicts.
i can restore the databases onto the dev server no problem.
my problem is that i also need to restore the repositories database onto the dev server plastic otherwise i cannot view the restored rep_ databases.
but the plastic on the server already has a repositories database with values in there, so i cannot restore over it otherwise i will lost whats there.
i would just like to know how i can restore the rep_ databases into plastic without having to restore the repositories database
if you have the database files, you can just relink them to the server using the next command:
$> cm addrep
Connect an existing repository by adding its database.
Usage:
cm addrepository | addrep db_file rep_name repsvr_spec
db_file The name of the database file on the database backend.
rep_name The name of the repository.
repsvr_spec Repository server specification:
[repserver:]svr_name:svr_port
All
I have built a windows form application using VS 2005 Standard edition which uses SQL Express as the database.
I'd now like to deploy my application to another PC that has .NET framework and SQL Server already installed.
The bit I am unclear about is what do I need to do to ensure that my database is also deployed with my application?
I have spent most of the day reading various articles from msdn to other blogs and I can't get a clear understanding on what is the best way to deploy my application. Some of the varying advice includes:
Add a 'setup' project and create a setup.exe file
Use a custom action to create a database during installation (uses installer class)
Manually detach .mdf and .ldf from database and use command line on target PC to reattach to database
Amend .config file to get new connection string (from target machine) and then reference that in my ado.net code
etc. etc.
Can anybody cut through the confusion for me and help me out?
Thanks
Here’s the simplest way I can think of:
Build the application
Copy the
executable (in the Bin directory) and
the app.config file to the other
machine. The executable and
app.config need to be in the same
folder
Backup the database on your
machine and restore it on the other
machine
Change app.config to point to
the restored database