IP Library Granted Patent US 8,572,035
Granted Patent B2
US 8,572,035 · App. 12/352,786 · Granted Oct 29, 2013

Universal data management interface

Inventor: Jasmin Cosic (Pittsfield, MA)
Assignee: Crucial Apex Communications LLC
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,572,035
App. No.
12/352,786
Granted
Oct 29, 2013
Kind
B2
Abstract

A universal data management interface (UDMI) system includes a processing system generates a visual interface through which a user can access, manage, and manipulate data on plural different types of remote databases. The UDMI connects to multiple standard database management systems and to allow multiple users to access, manage, and manipulate data within each of the multiple standard database management systems. The UDMI also allows multiple virtual databases that reside in a single database to be available as a network service.

Claims (47)

1. An apparatus comprising:

a memory configured to communicate with a processor and having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations comprising:

generating a visual interface for a first and second virtual database stored in a database management system, wherein the visual interface is operable to access and change data in the first virtual database and the second virtual database;

maintaining unique table names within the database management system; and

determining, in response to a creation of a new table within the first virtual database, whether the first virtual database includes a same table name as a new table name of the new table,

wherein in response to the first virtual database including the same table name as the new table name, presenting an error message through the visual interface, and

wherein in response to the first virtual database not including the same table name as the new table name attaching a unique identifier to the new table name.

2. The apparatus of claim 1 , wherein the database management system is compliant with one or more of:

an ORACLE system,

a MICROSOFT structured query language (MSSQL) server,

a SYBASE system,

an INFORMIX system,

a DB2-based system,

a dBASE-based system,

a standard query language (SQL)-based system,

a mini structured query language (mSQL)-based system, or

a MYSQL-based system.

3. The apparatus of claim 1 , wherein the operations further comprise storing a security table,

wherein the security table is independent of the first virtual database and the second virtual database,

wherein the security table indicates whether a login is to be permitted access, and

wherein the security table is transparent to a non-administrator.

4. The apparatus of claim 1 , wherein the operations further comprise storing an inactivity time for the visual interface,

wherein the inactivity time is independent of the virtual database, and

wherein the inactivity time comprises an amount of time between two subsequent executions of instructions.

5. A method comprising:

generating, by a computer based system, a visual interface for a first and second virtual database stored in a database management system,

wherein the visual interface is operable to access and change data in the first virtual database and the second virtual database;

maintaining, by the computer based system, unique table names within the database management system;

determining, in response to a creation of a new table within the first virtual database, whether the first virtual database includes a same table name as a new table name of the new table,

wherein in response to the first virtual database including the same table name as the new able name presenting an error message through the visual interface, and

wherein in response to the virtual database not including the same table name as the new table name, attaching a unique identifier to the new table name;

storing, by the computer based system, security information for the first visual interface and the second visual interface in a security file; and

storing, by the computer based system, an inactivity time associated with the first visual interface in a session identification file.

6. The method of claim 5 , wherein the visual interface is independent of a programming language used by a particular database management system for which the visual interface is generated.

7. The method of claim 5 , further comprising deleting a session record in the session identification file, responsive to a determination that an inactivity time exceeds an allowed time.

8. A method comprising:

generating, by a computer-based system, a visual interface for a first and second virtual database stored in a database management system,

wherein the visual interface is operable to access and change data in the first virtual database and the second virtual database;

maintaining, by the computer-based system, unique table names within the one database management system; and

determining, in response to a creation of a new table within the first virtual database, whether the first virtual database includes a same table name as a new table name of the new table,

wherein in response to the first virtual database including the same table name as the new table name presenting an error message through the visual interface and

wherein in response to the first virtual database not including the same table name as the new table name, attaching a unique identifier to the new table name.

9. The method of claim 8 , further comprising storing a security table that indicates whether a login is to be permitted access, wherein the security table is transparent to a non-administrator.

10. The method of claim 8 , further comprising storing an inactivity time, wherein the inactivity time comprises an amount of time between two instructions.

11. The method of claim 8 , further comprising manipulating relations among tables in the database management system.

12. The method of claim 8 , wherein the maintaining is performed by a table manager.

13. The method of claim 8 , wherein the unique identifier comprises an incremented number generated by a Sequential Number Generator.

Assignments (2)
MERGER Recorded Oct 9, 2015
From: CRUCIAL APEX COMMUNICATIONS LLC
To: S. AQUA SEMICONDUCTOR, LLC
Reel/Frame 036765/0659 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2010
From: COSIC, JASMIN
To: CRUCIAL APEX COMMUNICATIONS LLC
Reel/Frame 025079/0781 →
Continuity (4)
Continuation 11072030 · Mar 4, 2005
Continuation 10217937 · Aug 12, 2002
Provisional Application 60311863 · Aug 13, 2001
Related Publication 20100023541A1 · Jan 28, 2010