Development example

EUT up sizing example

Pro-Tech Co., Ltd.

By up sizing to SQL Server, I realize the speedup of duties and effective system management

In Access designed for a small database, I cannot avoid a decline and the competition of the transaction speed by the increase of quantity of data and the traffic. However, original program development takes a budget and time. I realized up sizing from a database system by Access which the employee made to SQL Server by the shift with the ADP file from a design of the electric equipment construction in a short term in construction, the professional technical center that I conserved it and checked Co., Ltd. around Yokkaichi-shi, Mie and realized large duties improvement.

● I unify inconsistent slip processing in Access

In the professional technical center Co., Ltd., each staff submitted necessary slip and documents in various form including 帳票 by handwriting and Microsoft Office Excel by completion from an order of the electric construction since the establishment of 1991. However, because count took time, and the data were saved to a PC of each person, I was very inefficient, and it was the present conditions that time suffered from basic intelligence. Therefore, for two years, I changed these to a system in Microsoft Office Access which Yoshiharu Yamaura of the company's EIM engineering department E.E. team watched the interval of duties and made overall. The PC number of client was the system which used one of those as database server by Access in 15.
After it was a written estimate, an ordering slip, a purchasing slip to be available as a system, and I took it for approximately a half year, and having adjusted various demands and small malfunction, it was operated in earnest.

● The joint ownership of data is difficult by the issue of communication line with the spot office

In the company, I might go to the spot office of the customer point company for spot construction for a long term, and, not the operation only for this office, the system which bound the spot and the head office together was expected. Therefore, as the next step, it linked the head office to the spot office with a communication line using Access and was to share data.
However, transmission rate was only an ADSL line of 1MB, and time suffered from what I was able to secure as a communication line by various circumstances to transmit and receive a large quantity of Access data in the head office in a lump. Therefore the data which I input in spot office and the head office made it a reproduction for a certain period of time each and changed it to a method to merge the data of the spot office which I made a reproduction into the data of the head office.
However, in this merge work, the problem that you must inspect because there was omission by the competition of data occurred, and it was necessary to cope immediately. Because "I was in charge of the system of Access by the additional post with the main profession, it was called even on a holiday when a trouble occurred and was serious work" (Yamaura).

● Easy up sizing to SQL Server

Therefore I secure a budget in order to improve the present problems in November, 2005 and will ask the outside company for system development. While I investigated a developer to depend on, the system development by Access and SQL Server led to in force with the reputation Co., Ltd. I thought about I programed it originally at first, and developing it, but I might say a budgetary problem and the succession of the operability, and the front end concluded that up sizing from Access to 2005 Microsoft SQL Server Standard Edition was most suitable for the database while using Access.
In a shift, I made an ADP file by Access up sizing Wizard from the analysis of the hearing of duties and the current Access database at the beginning and performed a shift to SQL Server by the Access project.
Of course the inspection is necessary because it is a shift of important mission-critical task. In the company, I took two months and inspected it about input, count and realized full-scale operation from April, 2006. A table and the query to be several hundred were able to shift without a problem.
"The shift was really smooth". There was the place that needed re-inspection partly, but the problem disappeared by inspection work and adjustment like the twice. In addition, line in itself did not change about the communication with the spot office either, but the delivery of data became able to perform it very speedily and was able to realize the head office and the environment that did not change (Yamaura).

● Merit to shift to SQL Server if I feel a limit in Access

The system by SQL Server which operated improved business efficiency of the company greatly. "At first transaction speed largely improved". In addition, I just used foam of Access, and there was not the sense of incongruity with the conventional system, and other staff came to be able to use the input immediately because I went in Access. Of course it became without uneasiness such as inspection work by the omission of data or the damage of the file (company's EIM engineering department Assistant Department Manager north shallows Keisuke). Because "there is not the data competition, for a system in the company, duties are largely improved". I think that I should have known SQL Server earlier. The which shifts to SQL Server if I feel it when it is a limit to some extent thinks that there is a merit very much than I perform where has a limit of Access in a feel state (Yamaura)
I distribute "an improvement seat" for an employee from August, 2006 to make use of SQL Server in duties as well as processing capacity and a performance gain more in the company and gather the refinement on input work and the system, methods to utilize statistics data effectively more and am preparing for more utilization now. In addition, I am going to perform more effective data communication by communication by the PHS using VPN with the spot office.
For data competition, the increase of the number of client, it will be I still utilize a database in the company which was settled by performing up sizing of a system positively, and to plan the efficiency of further duties.

Page top
Microsoft Partner