Im unable to get any connectivity to Oracle 7.3 using the current SSMA from Microsoft. There is no legacy download anymore and i think i need an older version, 6.0. I keep getting two-task connection potocol errors when I use the tnsnames method to define a service. This works with the schema manager in the legacy oracle tools but no matter what i try Im unable to get a connection in the new SSMA without seeing that error. I should say im on a windows 7 vm for legacy reasons.
I have tried using a linked server in sql 2008 and 2012 which would allow me to make views. I could then bring it into Entity Framework, which is the ultimate goal, but same result as above.
Anyone had a similar issue and happen to have an older SSMA?
Client/Server Interoperability Support [ID 207303.1]
For Oracle Server 7.3 you need oracle client 7.3 or 8.0.5-8.1.7 or 9.0
Oracle8 i 8.1.7 Documentation
To configure oracle client SQL*Net V1, V2 ,tnsnames.ora read SQL*Net FAQ
I installed Oracle 7.3 very long ago in 1996 :).
Update
You can migrate to the free version of the Oracle 11 XE version or use an RDS instance of Oracle in the Amazon cloud with free 1-year service .
Use the utility exp and imp. These utilities are no longer being developed and are not supported, but are necessary for migration from very old versions.
Migration plan:
Define the necessary schemes and users for migration in the source
database, table spaces.
Install the free version of Oracle 11 or create an RDS instance of Oracle in the Amazon cloud with free 1-year service.
Create the required tablespaces.
Create profiles, users and roles.
Import the dump file.
Make the migration in mssql.
Related
I'm currently working on a enterprise that uses TFS 2017, and we pretend to upgrade to Azure DevOps. So far I'm just studying about how to implement this TOOL. I'm new on devops things and I have these following doubts... Why do we need SQL Server to install DevOps Azure? What kind of information are stored in there?
In the server configuration wizard, I have the option to select an existing database to use for the Azure DevOps Server that's being deployed... Can I select the currently database that's used by TFS 2017?
Azure DevOps Server and Team Foundation Server store just about everything in massive SQL Server databases.
The main server configuration is stored in the tfs_configuration database and each project collection is stored in a separate database The default is tfs_defaultcollection.
The collection database holds all version controlled files (TFVC and Git), all work items (Product Backlog, Sprints etc), Test Cases and all test run attachments, your Pipelines, Builds and Releases as well as all of the artifacts produced by these pipelines.
These databases can grow considerably.
Whether you can keep your current database server depends on what version you're currently running. SQL Server 2016 SP1+ happens to be supported by both Azure DevOps Server 2020 as well as Team Foundation Server 2017. You could keep using that for the upgraded installation.
But my recommendation would be to install SQL Server 2019, you'll get all of the performance and security benefits of the new server, support for the latest Windows Server platform, as well as a support window that matches your new Azure DevOps Server installation.
You can find the SQL Server compatibility matrix for TFS/ADS here:
Azure SQL Database and SQL Server
TFS 2017 was one of the last versions to require a database for the Warehouse, which is a form of replicated data. Reports can be written to pull data from the warehouse, without impacting the user experience. The database is somewhat deprecated now, especially for reporting. Microsoft promotes the use of the API to pull data from the live database. TFS does however still need its "live" database to store all of the data presented to users. These will be work items, discussion comments, project templates, user mappings to AD, amongst other things.
You will need to upgrade your 2017 Schema to conform to the new standard as defined by Azure, which will be taken care of as part of the upgrade.
What kind of information are stored in there?
Issues, templates, build results, lots of things.
Can I select the database that's used by TFS 2017?
Yes, that will be upgraded during the installation.
I am trying to move my rapidly growing MS Access 2016 database to a SQL Server back end and build an asp.net front end. I am trying to migrate data from the Access database to an instance of SQL server 2014 but this is not going so well. I tried to migrate it using the MS Migration Assistant but this is not supported for versions after 2010. Does anyone know an easy way to convert Access tables to SQL Server?
Thanks in advance.
The only migration assistant that was depreciated was the one built into Access. So you are correct that after Access 2010, the migration system is removed.
However, there is a SQL Migration Assistant for Access that can be used here:
https://www.microsoft.com/en-us/download/details.aspx?id=54255
The above SSMA for Access is better than the old migration assent and is designed for upgrading Access to SQL server.
NOTE CAREFULLY that the shortcut on the desktop is for office x64 which FEW have, so make sure you launch the x32 bit version of SSMA – you find the shortcut to x32 in the programs folder (or just type I SSMA in windows 10 and select the x32 version.
AGAIN:
Make sure you follow above to launch the x32 version else it will not work.
Create your database in SQLServer
In Management studio, Right click on your database. Go to
Tasks
Import data
This should bring up the SQL Server Import and Export Wizard
In Data source, choose Microsoft Access. I have 3 choices in my test server. I'm not sure what one to use, so it might pay to play around.
Follow the Wizard, which should get you to were you want to be
To automate migration from Microsoft Access database(s) to SQL Server
SQL Server Migration Assistant (SSMA) is a free supported tool
A video tutorial and all procedure I posted on the blog:
https://www.imran.xyz/convert-microsoft-access-database-to-sql-server-database/
You can download it from Microsoft
https://www.microsoft.com/en-us/download/details.aspx?id=54255
i just joined a company and they have a hp_ux1020 that has oracle 7.3.4 on it. they now want to convert that to sql. i have windows 7 have no idea how or what to use to connect to that server remotely. I know nothing about linux. Thanks for your help.
Oracle 7 is an incredibly old version long out of support.
Converting a database is not a small task, depending on the complexity of the database, but is doable.
Depending on your experience, it may be best to hire a contractor that specializes in database migrations.
I suggest creating CSV (comma-separated values) files for each table and, from those, importing into your new Microsoft SQL Server database.
No modern client connects to Oracle 7, but it may be worth a try to use the oldest downloadable version of Oracle SQL Developer (1.3x I think). Oracle SQL Developer connects to Oracle 8 with an unsupported version warning, but I have not tested with 7.
You may have to go on a hunt to find a client old enough to connect to 7. Oracle typically does not provide clients for unsupported version of Oracle, even though they have all the necessary files.
Good day. :D
I'm in some trouble configuring BonitaBPM with Ms Sql database.
Already searched a lot on the internet but many of the examples used in mysql show, it tried to do the same, so that the problem that the files mentioned in the articles do not exist in my folders setup Bonita (Bundle, etc.).
I try to configure the file that links to BD's but gives a runtime error.
My goal is to use Ms Sql as the primary database, thus making the emigration of all tables in Bonita to SQL DB.
I would like to receive an example how to do this configuration.
Thank you already.
Actually Bonita BPM 6 can be configured to use Microsoft SQL Server 2012 (Bonitasoft provide official support for such configuration) but only with the JBoss bundle or other supported applications server such as Oracle WebLogic.
That is because:
Apache Tomcat is not a full Java EE application server
An extra library (Bitronix) is included to provide transaction management support
Bitronix has known issues with SQL Server
So only solution I may suggest is to switch to JBoss bundle, or, if possible, use an alternative DBMS such as PostgreSQL.
Sorry to not be able to come with a better option but here we facing a limitation of Bitronix library.
It appears out of the box the v1 of Microsoft Sync Framework would only support synching with a CE db, using the SqlCeClientSyncProvider. I can't find anywhere in the documentation about v2 if we can now sync between two SQL Server databases. Anyone know of hand if this is now possible (without writing my own client provider)?
The following provider is the one that you should be using to sync with a SQL Server database.
Microsoft.Synchronization.Data.Server.DbServerSyncProvider
The Local Database Cache tool could get you up and running fairly quickly without having to worry about these details - you would however be sacrificing some flexibility.
You don't necessarily need Sync Framework 2.0 if you do decide that you want to get a little closer to the metal but it has now been released and is probably your best bet. Just be careful with the DLL versions that you swap into your solution after installing the SDK. Note below that the database DLLs are not versioned consistently with the rest of the framework and that the version of the Microsoft.Synchronization.Data.SqlServerCe DLL actually decreases from 3.5 to 3.0.
Installing Sync Framework - MSDN
All database provider DLLs have a
version number of 3.0 rather than 2.0
because some of the providers were
originally released before Sync
Framework 1.0.
Microsoft.Synchronization.Data.SqlServerCe.dll
was originally released as part of SQL
Server Compact and previously had a
version number of 3.5 to match the SQL
Server Compact version. The version of
this DLL is now 3.0 to match the other
database providers.