The Institute for Clinical Evaluative Sciences (ICES) is seeking a Database Programmer to design and develop reports using inTool, their web-based reporting tool. The successful candidate will be capable of understanding and working with an existing SQL server database that contains data spanning a variety of health topics.

The position reports to the Director, Information Management, and involves direct collaboration with ICES Researchers, Epidemiologists, Programmers and Biostatisticians in the Monitoring and Reporting Department.

Qualifications/Skill Requirements:

Degree in Computer Science or related field
Minimum of 3 years relational database experience having strong SQL/TSQL programming skills
Experience with reporting tools, preferably MS SQL Server and related technology such as Reporting Services and Integration Services
Data warehouse concepts and practical, hands-on data transformation and manipulation experience
Excellent analytical, communication, documentation and organization skills
Able to work well independently but also team-oriented and comfortable collaborating with fellow Epidemiologists and Developers
Other/Nice to Have:

Experience in the health care sector and/or experience working with health information
Experience and/or familiarity with Crystal Reports, ASP.NET, VB.NET, and MS Office
Applicants should submit their résumé by Friday, April 30th, 2010, to the attention of:

Human Resources Department

E-mail: resumes@ices.on.ca

Please quote DP-01 on all correspondence.

We thank all applicants for their interest; however, only those invited for an interview will be contacted.

Source: Workopolis.com

Data profeDemonstrated experience and expertise with SAS programming language required.
Demonstrated experience using advanced Excel features and techniques required. Demonstrated experience in analysis and presentation of data required. Experience working with a variety of information systems and data files, including large and complex files: analyzing file structure, using and creating file layouts, transforming raw data into finished products. Familiarity with various types and sources of health care information, including financial and patient-level data files.

Familiarity with Washington State Comprehensive Hospital Abstract Reporting System (CHARS) desirable.
Experience with database application development (e.g., Microsoft Access) desirable. Strong communication skills, both written and spoken. Comfortable working independently, with experience working in a team environment. Skills in establishing and maintaining effective working relationships with WSHA members and staff. Physical ability to use computer hardware and software required. Ability to read, write, speak and understand English required. Educational, Experience and/or Licensing Requirements

Bachelor’s degree or higher in relevant field.
Undergraduate or graduate coursework in statistics, data analysis, research methods.
2-5 years experience in data analysis, decision support, including demonstrated proficiency with analytical software.

Data / Content Migration Assistant,
Data / Content Migration Assistant
data analyst
data analyst
data analyst
ENVIRONMENTAL DATA ANALYST
data analyst
data analyst
data analyst
data analyst
data analyst
data analyst
Analyst, Systems and Data
Marketing data analyst
Analyst
Data Administrator Competition No.
Health Information Analyst
Analyst, Research and Data Services
IT Data Steward 
584, Corporate Reporting Analyst
Research Analyst
Data Modeller
Decision Support Analyst,
Junior Research Analyst
Data / Content Migration Assistant, MSR/ECUSTOMS
Reporting Analyst
DATA CONSERSION SPECIALISTS
Reporting production analyst

When I joined the company in 1995 most of the accounting data was recorded in Manual registers ledgers / spreadsheets consequently extensive time was spent on preparing reports and making timely decisions.

In 1996, I initiated utilization of MS Access and led the logical data modeling of the Altech, and gradual implementation of RDMB format in MS Access. The data in MS Excel flat files was imported into MS Access and transformed into RDMS format. Created tables to store Master data about all accounts including customers, suppliers, employees and entity related to Altech business. Designed tables to record financial and material transactions and coordinated with Accounts departments to create general ledger and related reports in Crystal reports 8-9.

In 2000 this data base was upgraded to SQL Server 7 utilizing MS Access as front end using Access data project. All the data entry forms and reports were upgraded accordingly. From 2000 to 2002 all the data was centralized in a SQL Server database on server. This facilitates the in-depth business analyses through Crystal reports 9-10 and fast and correct data entry using MS Access Forms.

During the approximately 10 year of my first job, I learned and mastered several concepts of data management such as changing dimensions, notably how to keep track of historical data. For example every month company’s 300 production employees were rotated into different departments and issue was to produce employee historical reports. Database was extended to keep the monthly production activities of employees. New reports were developed in Crystal Reports in Crystal Reports 10 for example complete individual employee performance for any time span, departmental performance. Labor cost by production activities.

Automated the posting of inventory data to financial ledgers for example as soon as new raw material received it was stored in inventory table and updates vendor accounts and material accounts.

My first job set the foundation of database technologies, logical data modeling techniques like entity relationship diagram and translating these into physical model. Understanding of transact SQL Statements, Data input strategies and mastering Crystal reports software for preparing meaningful information, data cleansing/scrubbing and when to use to text files for data and spread sheets.

This data is posted into two tables with transact-sql statements  below statement 1 post the data into transactionz table as mentioned above and statement 2 post the same transaction into material ledger a/c after checking exisiting transaction ids by using ‘where not (tr_id = any (select trn from transactionz))’ so no duplicate transaction is posted as well if priceis 0 in case rate not finalized no transcation will be posted into ledgers though quantity is already received.

These statements made accounting entry very simple with 1 step i.e. once data is recorded in inventory it is automatically posted in effected ledger accounts accounts.

Statement-1

insert into transactionz  (trn, transactiondate, transactiondescription, accountid, credit, debit)

select  tr_id, transactiondate, cast(quantitycr as varchar)+ ‘ / ‘+ cast(quantity as varchar)+ ‘ ‘+ +cast([description/name] as nvarchar) + ‘ @ Rs. ‘ +cast(price as varchar) ,accountid,  (quantity*price), (quantitycr*price)  from view38

where not (tr_id = any (select trn from transactionz) and (price<> 0)

Statement-2

insert into transactionmat  (trn, transactiondate, transactiondescription, accountid, debit, credit)

select  tr_id, transactiondate, cast(quantity as varchar)+ ‘ / ‘+cast(quantitycr as varchar)+ ‘ ‘+ +cast([description/name] as nvarchar) + ‘ @ Rs. ‘ +cast(price as varchar) ,215,  (quantity*price), (quantitycr*price)  from view38

where not (tr_id = any (select trn from transactionmat) and (price<> 0)

In this example our client was facing an  issue where shipments are made  and C&F value amount is taken as Accounts Receivable, payments are received in 2 to 3  installments.  Management wants to know how much is outstanding against each shipment C&F Invoice.

In database invoice is generated on C&F basis where comprehensive information is recorded like invoice no,  Bill of Lading No, C&F Amount, Shipment NO and so on.

When Payments are received it is recorded exportpayments table along with shipment NO.

In order to create a report to what is outstanding against respective invoice we created a SQL Query  using select into Transact-SQL  as follows;

select sn1, sum(amt) as cfvl

 into #sd4

from dbo.exportpayments

group by sn1

Select Sn, CFvlu,sn1, cfvl, Cfvlu-cfvl as balance from

 dbo.invocesexpressions inner join #sd4 on

dbo.invocesexpressions.sn = #sd4.sn1

drop table #sd4

In the above example we selected Shipment NO SN1 and sum amount Sum(amt) as cfvlu

Into temp table SD4 and then we selected Shipment no SN, CFVLU from invoices table and CFVL from Temp table #SD4 and join Invoices table and #sd4 based on Shipment NO

At the end we dropped thetemp table  #SD4.

This example utilized the temp table for generating outstanding payments report.

Shipmnt              CFVLU          Shpmnt  Amnt RCD       Blnc

In this case Security departments overtime was calculated based on 12 hours and in all other departments base was 8 hours.

Salary was categorize by monthly type as [monthlytype] SG for Security Guard where ovetime was calculated based on 12 hours.

code is given below and was in included in select statement;

CASE monthlytype WHEN ‘sg’ THEN dbo.wrkshopattndnc.TOTAL_OVERTIME * dbo.[wrkshop employees].Salary / DAY(dbo.wrkshopattndnc.month)/12

ELSE dbo.wrkshopattndnc.TOTAL_OVERTIME * dbo.[wrkshop employees].Salary / DAY(dbo.wrkshopattndnc.month) / 8

END AS ovtamnt

We were getting answer like 8.67 products manufactured from 50 kgs of raw material. We talked to the manufacturing department they confirmed that 8 no of products are manufactured and 0.67 is the wastage. We calculated the weight of each product and then multiply by 8 which gave us the weight in kgs of 8 no of products.
After that weight of 1 product was multiplied with .67 of product and got the weight of wastage in kgs.
In the above scenario we needed the decimal value of .67 separated from 8.67 in separate column to show wastage. Our data was in SQL Server, we utilized the floor function to make 8.67 into 8 and then subtracted the 8 from 8.67. The issue was resolved by using floor function.

Below is the related information about Floor function as obtained from SQL Server books Online.

CEILING and FLOOR

The CEILING function returns the smallest integer greater than or equal to the given numeric expression. The FLOOR function returns the largest integer less than or equal to the given numeric expression. For example, given a numeric expression of 12.9273, CEILING returns 13, and FLOOR returns 12. The return value of both FLOOR and CEILING has the same data type as the input numeric expression.