Oracle SQL Developer is an integrated development environment (IDE) which provides editors for working with SQL, PL/SQL, Stored Java Procedures, and XML in Oracle databases.
Buzilla is easy to use and provides basic functionality to use as a bug tracking tool. If big size attachments are allowed it would have been great. Also with Bugzilla home->Test management area is improved by allowing multiple sections it would be awesome!
Almost all development activities (the tool is called "SQL Developer", not "DBA Toolset") can be done easily and quick with [Oracle] SQL Developer. From data model creation (tables, views) to development (creation of procedures, functions, packages) and then testing (SQL Developer includes an easy to use debugger), all tasks can be performed in a single tool.
It may not be as complete as other solutions for DBA tasks like instance monitoring, but it is usually OK for development and testing environments if you want to do some basic troubleshooting.
Open source! No license fee involved, no limit to the number of licenses.
Easy to install and maintain. Installation is very easy and hardly needs any maintenance efforts, except when migrating from one version to other. Each project can have its own group of users.
Includes all the core features/fields that are needed to log a software bug/issue.
Multiple attachments are possible, supports various formats.
Good for reporting. Filtering mechanism lets you query bugs by various parameters.
Object Browser in SQL Developer allows you to explore the contents of your database using the connection tree.
The SQL Worksheet is an editor that allows for execution of SQL statements, scripts, and PL/SQL anonymous blocks. SELECT statements can be executed to return results in a spreadsheet-like 'grid' or can be executed as a script such to emulate SQL*Plus behavior and output
DBA Console allows users with administrative privileges to access DBA features such as database init file configuration, RMAN backup, storage, etc.
Cloud Based. I'd like to see bugzilla be cloud based. The company I currently work with made a final decision to change db's for this specific reason. Due to the frequency of travel in this company, they need access to bugzilla from differing national / international locations.
Larger File Attachments. I believe the limit of a bugzilla content upload is 4 megabytes. For many of our video'd issues, this file size is simply impractical without the additional effort exertion on video compressor applications.
Inability to run multiple queries on the same database. You can only run one query on a given database.
Analytical models created from complex tables isn't accurate, and needs work.
Inability to view multiple tables of a database side-by-side. When trying to find correlations between tables, it would help to be able to see them at once on the same page.
For future projects I will look at something that is hosted in the cloud that I don't have to manage. I would also like something that has a more modern feel to allow my customers to use it as well as my employees.
This is a pretty straightforward system. You put in the bug details, a ticket is created, the team is notified. The user interface reflects this very simple and straightforward flow. It's certainly much easier than trying to track bugs with using Excel and email.
Oracle SQL Developer is very easy to use and there are a wide range of courses available which can help you get started just within a day. Data can be exported in multiple formats based on user requirements. Organizational data can be stored and management effectively using Oracle SQL Developer. All the data, tables, sequences, indexes can be easily created and updated in Oracle SQL Developer.
Since it is open source, it doesn't have customer service. However, the amount of information on forums is vast. If you can wade through it, you'll get what you need
Implementation was pretty simple. Particularly because the product cannot be customized so there is not much to do apart from getting it up and running.
We migrated away from the whole suite of Rational tools because of their massive complexity around administration and inflexibility regarding workflows. In addition, the suite was insanely expensive, and users hated the usability of the tools. We evaluated, and liked JIRA, but because the organization was looking for cost savings, we ended up going with Bugzilla and it's FOSS model so as to avoid ongoing costs.
I have started to use Toad for Oracle recently because it is easier to sort and filter results, due to their memory sort feature that puts the results from your query in memory so that you don't have to rerun your query. I have used SQL Developer to easily update records in tables that I need to fix. I haven't found an easy way to do this in Toad other than writing SQL insert statements.
It has made the SDLC process more efficient. Bugs were logged and tracked in emails or in Excel sheets leading to slow communication and at time version issues with multiple files. Being an online tool, Bugzilla solved those issues, improved communication, instant status updates and improved efficiency.
We have used Bugzilla with a lot of federal goverment agencies (DHS, CMS, SAMHSA, CDC, HHS etc). Project Directors adn Principle Investigators were at times given access to Bugzilla which provided a snapshot of open vs closed issues.
Some groups would resist using Bugzilla with the email reminders being the main reason. Turning off or reminding them of features where we can 'control' email notification helped a lot.
