Interested to know if anyone has had any experience with moving a VB6 application from SQL Server 2000 to a newer version of SQL Server.
There are VB6 legacy apps on a Windows 2000 Server
These VB6 apps connect to a SQL 2000 Database
We are looking to upgrade from SQL 2000 to SQL 2014
We are reporting with Crystal Reports
The VB6 apps have inline SQL within them
I'd like to understand what the possible implications could be?
Thanks
For one thing, there is no direct migration path from 2000 to 2014. This article (http://sqlmag.com/sql-server-2014/sql-select-steps-migrate-sql-server-2000-sql-server-2014) outlines some potential steps to take to perform the upgrade.
Things that may trip you up not mentioned in this article:
DTS no longer exists so if you have any DTS packages, it will be a project to upgrade/convert them all over to SQL Server Integration Serices (SSIS) packages.
If your VB6 app contains hard coded SQL statements, rather than just calling stored procedures, you could have minor syntax issues that would have to be rectified (so test EVERYTHING)
If you are also looking to migrate VB6 to .NET, there is an upgrade wizard out there somewhere, but it is HORRIBLE, so depending on the need, it may be faster to just re-write from scratch. If you are implying that the VB6 application would just connect to the migrated 2014 database, the note on the main question is accurate, but again...test EVERYTHING.
3a. If you are referencing any old COM components or old OCX controls, it will be a source of pain.
3b. Does your app do any reporting? old 2000 SSRS, or Crystal reports? again, another project.
Good luck!
I've done it, and there were stored procedures / user functions that needed to be updated for compatibility. Here is a Microsoft tool, SQL Server Upgrade Advisor. If you are using inline SQL in your code I'm not sure if this tool will help you. I was fortunate in that most on teh application SQL was implemented as stored procedures inside the database itself.
Here is an MSDN blog post about upgrade considerations and using the Upgrade Advisor tool.
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 8 years ago.
Improve this question
Apologies beforehand if I've been an unlucky searcher, but I feel like I'm either using the wrong keywords or there is nothing to find on the subject.
A colleague of mine has been using MS Access for decades and has no experience with other SQL tools. Most of the systems in our organisation are built on Oracle databases (and in quantities too large for MS Access), so data integration is often complex for him. To facilitate things, he will be moving his data sources to one of the Oracle servers, and will be able to access that data with Oracle SQL Developer.
All I'm able to find on the internet is how to migrate data but I'm looking for functionality differences from the perspective of a data analyst or a reporting developer, who works with preparated data.
I tried explaining it in simple terms, such as: "there are tables here as well", or "Oracle views are like Access queries", but there's a lot of ground to cover and I'm looking for some handles.
Do any of you know of a good source to read on this subject? Books, videos, articles, websites, anything. If at all possible, it should be in terms familiar to an MS Access user.
You not make it clear what developer tools you plan to replace Access with. Remember Access has two parts. The database part (the data engine). The data engine allows you to build tables, and execute SQL queries to retrieve data. This is also what the Oracle database allows you to accomplish.
Then there is the developer part. That is the part that lets you build forms (to edit data) and that of reports. This part is NOT part of the database engine (for Access or oracle).
So the differences in the database engine are NOT that important here, but MOST important is what tools you plan to build the reports and forms to edit data with?
You can most certainly continue to develop your software using Access. So Access has a VBA programming system, has the ability to develop forms, and also that of reports. However the database engine and table can be form the Oracle database.
So your question shows much confusing here since you not making any distinction between the developer tools (Access), and the database system you choose to WORK WITH Access. Access is a developer tool, much like VB6, c++, vb.net etc. It allows you to build reports and write code and build a user interface. A database system such as ACE, or Oracle or SQL server has no such ability.
The Access database engine (used to be called JET and is now called ACE) is a separate issue.
So a developer writing some software in say vb.net can choose to use the Oracle database system or can use the Access database engine called ACE.
It not clear if you plan to continue to use the Access development system, and then choose an appropriate database system such as SQL Server, MySQL or in your case Oracle as the database engine to work with Access.
If you plan to not use the Access development system to build reports and forms and write code, then you have to share with everyone here what tool(s) you plan to use. Since it sounds like the user is being dictated that they MUST use Oracle as the database system, then it likely that what developer tools such as vb.net, C++ or perhaps MS Access is also going to be forced upon the user.
Until such time you expand on what developer tools which are SEPARATE ISSUE from the database system is shared here, then any real answer is sheer speculation and a waste of our time.
So keep in mind that the Access databases engine, or SQL server, or Oracle or MySQL are database engines. AFTER you choose the database engine/system, you can then write code + forms in something like:
Vb.net
MS Access
Asp.net
Etc. etc. etc .etc
You also choose such systems as SQL reporting services, or whatever oracle has these days.
So if you crystal reports with ACE (the Access database engine), or you use crystal reports with SQL server or Oracle, then the feature set in crystal reports is VERY MUCH THE SAME in all cases.
And you might use MS Access reports with Oracle or SQL server or often the ACE (the default database engine for Access).
The user can continue to use Access as the user “interface” developer tool, and the data can be in any industry database engine that supports ODBC. The database system does not have nor include the user interface and reporting tools.
You not shared what reporting and development tools you plan to use with Oracle. As to what tool, well that like asking what kind of car to drive or what software development system should one choose. We don’t even know if the user has a choice. If they have a choice then they can continue to use Access and you have no need for a question here!
This question already has answers here:
Compare SQL Server Reporting Services to Crystal Reports [closed]
(18 answers)
Closed 9 years ago.
I'm going to develop an application...Just wondering...
What are the difference between SSRS and Crystal Report?[Visual Studio 2010]
Can you provide pros and cons?
I have used both Although Crystal Reports is very well know and widely used. It can be a hassle at times (Not saying that SQL Server reporting services is not a hassle sometimes.)
Pros for Crystal Reports
May people use it and understand how to use it. Its ability in the
creation of more basic to intermediate reports quickly is a plus.
Even if you don't know SQL you can still fiddle with Crystal Reports
to get the result you want, and flatten out the data. Supports
Dynamic Cascading Prompts (version XI and Higher) Supports Web
Viewer, ActiveX, Java and HTML.
Cons for Crystal Reports
Crystal's Report Design Component seems to be full of strange
scenarios. I believe because the software has changed hands so many
times. Documentation is pretty limited for the Report Design
Component. A beginner can definitely create a nice formatted report
quickly and easily, but when it comes to more complex reports where
performance is needed. Going back to understanding SQL is necessary.
Pros for SQL Server Reporting
Web Based Reporting Server Report Rendering Engine supports a number
of formats (Excel, HTML, Image, and more) Publishing and scheduling
is a part of Reporting Services. In crystal you need Crystal Reports
Server or Business Objects Enterprise for Publishing and scheduling.
Or you would need to create your own custom app) Parameter prompting
is nicer in my opinion Saved Data sources can be accessed by excel
users. User login an permissions are built in. Subscriptions are a
built in feature
Cons for SQL Server Reporting
It can sometimes be a pain to implement the Report builder feature
for building simple reports is somewhat limited The best report
builder is Visual Studio's Business Intelligence Studio. This is only
a con because for a beginning end user this could seem overwhelming
In all SQL Server Reporting Services is my pick.
I am using Visual Studio 2008 C# and SQL for my development.
Which oracle version should i download? Oracle 10g?
Does it have a design interface like sql server mangement studio?
Will this distribution concept have a graphical tool which say "Hi, on which servers would you like to distributed the database and on what basis"?
Using a local application, when I connect to its server and try to enter or delete data not on that server, will the oracle DB management system transparently access other servers to get or insert data? Or will it produce an error?
In reverse order:
Oracle does not do distributed in the way you (seem to) imagine. It's not Voldemort or Cassandra. It's one database per server, unless you're talking about RAC: but RAC is shared everything, so it's transparent (but way complicated).
The nearest Oracle has to SQL Server Management Studio is, I guess, Enterprise Manager. But I suspect OEM is probably not as easy to use as its MSSQL counterpart.
If you have a free choice use 11gR2. Why wouldn't you not use the latest version?
Oracle does support one application using multiple databases. However, this is normally due existing (even legacy) databases providing some of the data for an application. You should not deliberately set out to have separate databases on multiple databases, because distributed transactions are slower, less reliable and harder to tune. Find out more.
If you want to have multiple servers for resilience or scalability then as I said before RAC (Real Application Clusters) is Oracle's solution. This is a different architecture from SQL Server's federated approach. Find out more.
"so this link thing is support by free
versions of oracle?"
There is only one free (as in free beer) version of Oracle, and that is the Express Edition (currently still 10g only). That edition does support Database Links. I suggest you read two related articles by Lewis Cunningham: one explaining about DB Links and the other on linking multiple XE instances.
Oracle 10g Express is a great starting point. You would then need the Oracle Developer Tools for Visual Studio package.
Although the database comes with a fairly basic web-based interface, you would fare much better using a proper tool as Oracle SQL Developer (it's free). It's possibly not as complete as SQL Server Management Studio in terms of what it graphically offers, but it's good enough.
The difference between connecting a database hosted on your local computer and one hosted 450 miles away usually boils down to correctly configure your connection strings. However, it will not ask you 'graphically'; in the C# application you will be creating, you'd have to configure that by the way of code. Oracle SQL Developer, on the other hand, will ask you kindly. :)
Your local application would operate over the database instances which you have set it up to do so. You could configure your application to connect to 3 (or more) different databases, and it's not that the database system will know, but that you would be the one managing the operation.
I developed an application that uses Delphi 7, ADO and ORACLE, the provider I use is OraOLEDB (I need use this provider because the BLOB fields support). now I want to distribute this application with the provider. I search the web to download the Oracle provider, but has a size of 174 mb. I need to install this file on all client machines ? there is a smaller distribution of this file?
UPDATE
i am looking for a lightweigth (small) distribution of the OraOLEDB.
Thanks in advance.
I would opt to let the user supply it's client library himself. You avoid problems where there might me different oracle OleDb versions for different Oracle versions, licensing issues, installation issues etc. etc.
As fas as I know you need the package of 170 MB+.
It seems the distribution license (http://www.oracle.com/technology/software/popup-license/distribution-license.html) from that page allows you to redistribute the OleDB driver as long as you comply fully with that license. That is the official Oracle distribution - usually Oracle setups are large - if you don't want to include them on your distribution media you can simply point them to the download page.
Update: there is a smaller package in the InstanClient download page, look for Instant Client Package - ODAC here: http://www.oracle.com/technology/software/tech/oci/instantclient/htdocs/winsoft.html
I know a little bit about installing OLE DB providers, but I do not know anything about the Oracle provider, so this may not be practical. I see that the 174MB download includes a number of drivers (ODBC, .NET, OLE DB, etc.). I should be possible (but maybe not useful in the real world) to create your own distribution with the necessary files. One very nice thing about OLE DB is that it is typically "simple" to install. Running regsvr32 /i provider.dll will make the necessary registry updates to make it usable on a system. The providers I have used do not require a bucket full of registry hits like ODBC drivers often need.
So it might be possible to create your own distribution package. This site lists the files that are apparently necessary for the provider. I do not know if there are other "generic" files common to all Oracle client kits that might be necessary (that may be the part that would make this idea impractical).
This is the main problem when developing for oracle, except if you use ODAC, which has direct connection to oracle, without installing oracle client on clients' machines.
and it's much faster than using ADO or OLE DB providers.
Distributing Oracle client application can be a nightmare, even more today when you have 64 bit Windows.
Which version of the Client would you have to install? You need a 32 bit version for your Delphi application. But what if other programs do need having access to the 64 bit version? You need several ORACLE_HOME, with duplicated settings, or force you DotNet code to run in 32 bit mode.
I first wrote a Delphi wrapper using OleDB, then I realized how difficult it was to deploy it when using the Oracle DB. The same exact issue as yours...
Then I wrote a dedicated version, calling directly the OCI library. Speed was there (2 to 5 times faster than OleDB), with easy deployment.
You can use the latest version of the Oracle Instant Client provided by Oracle - see this download link - which allows you to run your applications without installing the standard (huge) Oracle client or having an ORACLE_HOME. Just deliver the dll files in the same directory than your application, and it will work.
The drawback of this solution is that it's not compatible with the DB aware components. But if you are using TQuery directly, then map the results in Delphi classes, it could be a great solution.
I need to build a simple, single user database application for Windows. Main requirements are independence from windows version and installed software. What technologies (language/framework) would you recommend? My preference for language is the Visual Basic.
EDIT: What about VB.Net and SQL Server Compact Edition?
I would recommend Sqlite. It's completely self-contained, and public domain so there are no license issues at all.
Single user or multi user?
For single user, the answer would be SQLite
For multi user (or multithread), try MySQL or PostgreSQL.
Since your requirement is a windows based application i would suggest that you go with sql server 2005 express edition which is a free tool, but with certain small limitations. you can upgrade to a bigger version when you go with a paid version.
There are other DB engines like SQL Lite or FireBird, choose them if the support and growth options they provide are good enough for you
Additionally, Visual Basic is eof lifed. VB.NET might be a better windows based platform currently. It would give a better platform / features to start with and when you want to expand the talent you have working on the project, i assume .NET talent might be more available than programmers who want to work with a dead language.
duplicate of What options are there for a quick embedded DB in .NET?
I'll repeat my answer from there:
"Or theres Esent, the built in database that exists in every copy of windows. Read about it here: http://ayende.com/Blog/archive/2008/12/23/hidden-windows-gems-extensible-storage-engine.aspx" and http://www.codeplex.com/ManagedEsent
SQLite will work for a local desktop application. If you want several users, a few gigas of data, and multiple connections I would use mysql or Firebird.
http://www.mysql.com/
http://www.firebirdsql.org/
FireBird SQL server will be thing of choice. It can be used in both embedded and multiuser mode like traditional databases. It implements many of the SQL standards and has strong community base. It is available for Windows, Linux, Solaris, OS X, HP-UX
As mentioned, SQLite is a great single-user database. This page has VB/SQLite examples. Once concerns is that SQLite parses foreign key constraints, but does not enforce them. You can use this code to generate "foreign key triggers" for SQLite, thus gaining an easy to use database with FK constraints.
Depending on how demanding your database needs are, though, you might want to consider MS Access.
I used SQL Server Compact Edition. It's like sqllite. A single SDF file accessed using ADO.NET.
You can develop your application using Visual Basic .NET and manage you database (add tables, columns, constraints, etc...) using Visual Studio.
SQLite may be what you are looking for. http://www.sqlite.org/
Depending on your needs for the application.
You could use SQLLite which is a very nice database with no installation required.
You could also use Microsoft SQL Server: SQL Server Compact 3.5.
Both are free!
It's not quite clear from your post whether you want a web application or not.
For a web application, MySQL works effectively on the Windows platform. You also have nearly limitless options for development environment including, PHP, Ruby on Rails, Django, and .Net.
If you are looking at a desktop application, MS Access might be suitable ... incredible easy for simple applications.
Well, assuming you don't have any prior experience...
You need some kind of persistence storage (for example a database) and a client.
For the storage you could use almost anything. For example you could create your DB in MS Access and just ship it as a file, using ADO to access it.
Other options are MS SQL Express edition (comes pre-installed on some machines or could be installed for free) and plenty of open source databases like SQLite
For the client side you could not go wrong with VBScript and ADO (using OLE DB drivers). They come with every Windows installation since Dark Ages, you will have plenty of references/tutorials/answers online.
A drawback: no UI to speak of, so you'll have to build a command line interface (which was for a 'simple' application).
If you want to build a UI I would suggest using .NET WinForms. The overhead will be substantially bigger but .NET is now installed on all XP/Vista machines and even if it is not you could always install the framework with you application.
If you want to build application that can move to other pc easily,I prefer Microsoft Access it is small database easy to use and no need to install.It suites for application like Addressbook,mini crud system.
But if you want to develop enterprise database system you should use MySQL instead.
I do not understand what you mean with "independence form [...] installed software". You ever need at least the DBMS installed as well as one client or user interface.
I recommend using MS Access. It is easy and cheap for simple, single user tasks and rapid prototyping development. Only development version have to be bought ("normal" Access) to create DBs. Runtime version of Access 2007 can be downloaded free of cost from Microsoft Homepage - for using only the database you created.
Also it combines DBMS and GUI frontend in same tool.
Dare I mention MS Access...?
If you are looking for small footprint (up to a few MB) and easy deployment (end-user should only install your application to get it working), then your options are SQLite and Firebird embedded.
Of those two, I'd pick Firebird any time, because of it's full support for SQL (you can't, for example, drop a column in SQLite), ACID compliance, and ability to go client/server without any changes (just change the connection string from embedded to server) to the code if you ever decide to let multiple users work on the same database.
Not to mention that you can use full server to develop (which means your application and database administration tool can be connected to database at the same time).
I'm successfully using Turbo Delphi (free for commercial and no commercial use) + ZeosLib (zeos.firmos.at).
The only things you need to distribute with your .exe are the database client dlls (no need to install the client, just put the dlls in the same directory).
Would Kexi work?
I can recommend from personal experience "My Visual database"
free, no code, no sql, just drag and drop.
http://myvisualdatabase.com/
Best Option would be to create a Win32 native application using Delphi and use SQLLite as the database.
Reason being Delphi can produce native win32 applications without any other product being installed on the machine.