Question

Considerations for commit frequency in Oracle / Pl*Sql

Asked by: williampeck

I have a procedure that processes anywhere from 1M to 4M records. Basically it moves it from table A (staging) to table B (final production).

The commit frequency is 100 records !

I'd like to increase this to something big, like 10,000.

The code queries all unprocessed records, then updates to "loaded" after 100 records, then queries again all unprocessed records, etc. etc.

So if I am processing 4,000,000 records, the cursor is being executed 40,000 times !

So by increasing to 10,000 it seems like I can reduce the overhead a lot.

so am I looking at this correctly? anything else to look at?

This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

Plus...

30 Day FREE access, no risk, no obligation
Collaborate with the world's top tech experts
Unlimited access to our exclusive solution database
Never be left without tech help again

Subscribe Now

Asked On: 2009-05-11 at 13:30:51ID24399397
Tags: Oracle
,; PL*Sql
Topics: Oracle CRM
,; PL / SQL
Participating Experts: 2
Points: 125
Comments: 18

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

"The time we save is the biggest benefit of Experts Exchange to Warner Bros. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange." Mike Kapnisakis, Warner Bros.
"Our team likes having a resource that is more secure than just using Google and most experts using this service really know their stuff. It's nice to look here first versus using Google." Dayna Sellner, Lockheed Martin
"Anytime that I've been stumped with a problem, 9 out of 10 times Experts Exchange has either the accepted solution or an open discussion of the potential solution to the problem." Kenny Red, eBay Inc.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.

Screenshot of Experts Exchange Knowledgebase

Need individual assistance?

Our experts are ready to help.

If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.

Want to learn from the best?

Read articles from industry experts.

Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.

Working on a long term project?

Store your work and research.

Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.

Access the answers to your technology questions today.

Subscribe Now

30-day free trial. Register in 60 seconds.

What Makes Experts Exchange Unique?

Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Trusted by the world's most respected brands.

image of each brand's logo

Faithfully serving IT professionals since 1996.

Experts Exchange Logo

Try it out and discover for yourself.

Subscribe Now

30-day free trial. Register in 60 seconds.

Free Tech Articles

WARNING: 5 Reasons why you should NEVER fix a computer for free.
It is in our nature to love the puzzle. We are obsessed. The lot of us. We love puzzles. We love the challenge. We thrive on finding the answer. We hate disarray. It bothers us deep in our soul. W...
SCCM OSD Basic troubleshooting
SCCM 2007 OSD is a fantastic way to deploy operating systems, however, like most things SCCM issues can sometimes be difficult to resolve due to the sheer volume of logs to sift through and the dispe...
Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2
This guide is intended to provide step by step instructions on how to migrate from Small Business Server 2003 to Windows 2008 R2 with Exchange 2010. For this migration to work you will need the fo...
Create a Win7 Gadget
This article shows you how to create a simple "Gadget" -- a sort of mini-application supported by Windows 7 and Vista. Gadgets can be dropped anywhere on the desktop to provide instant information, ...
Outlook continually prompting for username and password
There have been a lot of questions recently regarding Outlook prompting for a username and password whilst using Exchange 2007. There are a few reasons why this would happen and I will try to cover t...
Backup Exchange 2010 Information Store using Windows Backup
There seems to be quite a lot of confusion around the ability to backup Exchange 2010 using the built in Windows Backup feature. This stems from the omission of this feature prior to Exchange 2007 s...

Cloud Class Webinars

Avoiding Bugs in Microsoft Access
Alison Balter takes and in-depth look at avoiding bugs in Access. In this webinar you will learn about using the immediate window to debug your applications, invoking the debugger, using breakpoints to troubleshoot, stepping through code, setting the next statement to execute, ...
Top 10 Best New Features in Visio 2010
Scott Helmers gives live demonstrations of the top 10 new features in Visio 2010. This webinar will teach you how to create compelling diagrams by adding shapes to the page with a single click, linking the shapes in a diagram to data in Excel (or SQL Server, or SharePoint), ...
IT Consultant Business Secrets Revealed
Michael Munger, Experts Exchange tech pro and IT consultant, pulls back the curtain on his very successful businesses and answers question on every IT consultant and business owner should know about. He shares secrets on what he did to solve the 5 most common problems in IT, ...
Disaster Recovery and Business Continuity
Quest CTO, Mike Billon, gives an overview of the steps involved in building a dunamic disaster recovery plan. Through case studies and an examination of software/hardware tooles for monitoring and testing, you'll gain a better understandin of where you are, where you want ...
Organize Your Visio Diagrams with Containers and Lists
Scott Helmers uses cross functional flowcharts, wireframe diagrams, data graphic legends and seating charts to teach you: how to ustilize all three new structured diagram components in Visio 2010, the best practices for organizeing shapes in previous version of Visio, how to organize ...
How to Us Objects, Properties, Events and Methods in Microsoft Access
Alison Dalter gives an in-depbth look at objects, properties, events and methods in Microsoft Access. In this webinar you will learn about using the object browser, referring to objects, working with properties and methods, working with object variables, understanding the ...

Watch More

Join the Community

Give a Little. Get a Lot.

Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.

Join the Community

Answers

by: sundar62Posted on 2009-05-11 at 15:20:25ID: 24359611

Please check to see if the attached link answers your question.
http://forums.oracle.com/forums/thread.jspa?threadID=361756

by: sdstuberPosted on 2009-05-11 at 16:46:04ID: 24360054

yes, that's the right idea, but you may also want to consider just moving the data directly.

or, consider skipping the step completely.

why are you moving from A to B?

if A is just staging, why does it exist? Could you load directly into B from whatever source "stages" into A?

can you post your code? If you "must" process from A to B, and if you "must" process it in pl/sql then the previous post contains useful information about doing the bulk operations.

However, that's still sort of a second-to-worst case scenario (worst being row-by-row), if you can avoid or minimize the amount of pl/sql processing and just do the move in sql that would be best.

by: williampeckPosted on 2009-05-12 at 07:32:37ID: 24364990

sundar62, thanks but I am making as small a change as possible to the code, which inserts one record at a time. So I may do bulk inserts in the future but for now am just considering changing the commit frequency from 100 to 10,000 and trying to gauge any impact.

by: williampeckPosted on 2009-05-12 at 07:37:08ID: 24365038

sdstuber,

>>why are you moving from A to B?
- it's a legacy system so can't really change that.

>>the previous post contains useful information about doing the bulk operations.
- yes, we have discussed that but that is still around the corner. For now, I just want to increase the commit frequency as a quick fix with potential fair to moderate results.

So, yes, I am in the worst case scenario but trying to improve slightly with a quick fix.

this might buy me a little time and then will move to bulk inserts.

So . . . any impact I should consider by increasing the commit frequency from 100 to 10,000

by: sdstuberPosted on 2009-05-12 at 08:06:00ID: 24365411

please post the code

by: sdstuberPosted on 2009-05-12 at 08:07:49ID: 24365432

decreasing the frequency of commits means you'll be consuming more rollback/undo in each transaction. If you're doing updates you'll be locking more records and holding those locks longer.

Depending on the actions you may consume other resources like temp as well. it's hard to say without knowing what you are doing.

by: williampeckPosted on 2009-05-12 at 10:53:13ID: 24367180

>>decreasing the frequency of commits means you'll be consuming more rollback/undo in each transaction.
- did you mean increasing ? I want to increase the commit freq from 100 to 10,000

code posted . . .

  FOR cust_rec IN cust_curs(min_seqno, max_seqno)
  LOOP
-- save identifying data for err_tbl, if necessary;
    curr_seqno := cust_rec.cust_seqno;
    curr_srce_sys_cd := cust_rec.cust_srce_sys_cd;
    curr_cust_id_nbr := cust_rec.cust_id_nbr;
 
    srce_tot_in := srce_tot_in + 1;
 
-- insert into CDR (stage_final) cust table;
    INSERT INTO stage_final.cust
        (cust_seqno ,cust_id_nbr ,cust_chngd_dt ,cust_srce_sys_cd ,subr_cust_seqno ,subr_cust_id_nbr ,subr_cust_srce_sys_cd ,medl_rec_nbr
        ,cust_home_phon_nbr ,cust_home_fax_nbr ,cust_home_emal_addr ,cust_orig_efft_from_dt ,cust_contus_cov_reas_cd ,cust_contus_cov_efft_dt
        ,cust_prfx_nm ,cust_1st_nm ,cust_mid_nm ,cust_last_nm ,cust_sufx_nm ,cust_sex_cd ,cust_ssn ,cust_etncy_cd ,cust_brth_dt ,cust_dth_dt
        ,cust_marl_stus_cd ,cust_caus_of_dth_cd ,cust_pl_of_dth_cd ,cust_lang_cd ,cust_home_phon_ext_nbr ,cust_home_fax_ext_nbr)
      VALUES
        (cust_rec.cust_seqno ,cust_rec.cust_id_nbr ,cust_rec.cust_chngd_dt ,cust_rec.cust_srce_sys_cd ,cust_rec.subr_cust_seqno
        ,cust_rec.subr_cust_id_nbr ,cust_rec.subr_cust_srce_sys_cd ,cust_rec.medl_rec_nbr ,cust_rec.cust_home_phon_nbr
        ,cust_rec.cust_home_fax_nbr ,cust_rec.cust_home_emal_addr ,cust_rec.cust_orig_efft_from_dt ,cust_rec.cust_contus_cov_reas_cd
        ,cust_rec.cust_contus_cov_efft_dt ,cust_rec.cust_prfx_nm ,cust_rec.cust_1st_nm ,cust_rec.cust_mid_nm ,cust_rec.cust_last_nm
        ,cust_rec.cust_sufx_nm ,cust_rec.cust_sex_cd ,cust_rec.cust_ssn ,cust_rec.cust_etncy_cd ,cust_rec.cust_brth_dt
        ,cust_rec.cust_dth_dt ,cust_rec.cust_marl_stus_cd ,cust_rec.cust_caus_of_dth_cd ,cust_rec.cust_pl_of_dth_cd
        ,cust_rec.cust_lang_cd ,cust_rec.cust_home_phon_ext_nbr ,cust_rec.cust_home_fax_ext_nbr);
 
-- update record;
    UPDATE stg.cust
      SET status_cd = 'L'
      WHERE cust_seqno = cust_rec.cust_seqno;
 
    srce_tot_out := srce_tot_out + 1;
 
-- check to commit, -- xxx
    rec_cnt := rec_cnt + 1;
    IF rec_cnt >= c_commit_limit THEN <-- commit limit is 100, I want to increase to 10,000
      COMMIT;
      rec_cnt := 0;
    END IF;
 
  END LOOP;

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:

Select all Open in new window

by: williampeckPosted on 2009-05-12 at 10:57:20ID: 24367234

for the loop, it runs this cursor each time . . .

cursor cust_cur
SELECT *
FROM stage1.cust
WHERE cust_seqno
BETWEEN in_min_seqno AND in_max_seqno
AND status_cd IS NULL <-- so each time this cursor is run, the record set is smaller as records are updated (100 at a time)
ORDER BY memb_seqno;

by: sdstuberPosted on 2009-05-12 at 11:09:57ID: 24367433

increasing the limit decreases the frequency of commits.
so, different words, but we meant the same thing.

however, do you really need to do this in a loop?
could you just do one insert and one update with a commit at the end?

INSERT INTO stage_final.cust(
                                 cust_seqno,
                                 cust_id_nbr,
                                 cust_chngd_dt,
                                 cust_srce_sys_cd,
                                 subr_cust_seqno,
                                 subr_cust_id_nbr,
                                 subr_cust_srce_sys_cd,
                                 medl_rec_nbr,
                                 cust_home_phon_nbr,
                                 cust_home_fax_nbr,
                                 cust_home_emal_addr,
                                 cust_orig_efft_from_dt,
                                 cust_contus_cov_reas_cd,
                                 cust_contus_cov_efft_dt,
                                 cust_prfx_nm,
                                 cust_1st_nm,
                                 cust_mid_nm,
                                 cust_last_nm,
                                 cust_sufx_nm,
                                 cust_sex_cd,
                                 cust_ssn,
                                 cust_etncy_cd,
                                 cust_brth_dt,
                                 cust_dth_dt,
                                 cust_marl_stus_cd,
                                 cust_caus_of_dth_cd,
                                 cust_pl_of_dth_cd,
                                 cust_lang_cd,
                                 cust_home_phon_ext_nbr,
                                 cust_home_fax_ext_nbr
           )
    (SELECT cust_seqno,
            cust_id_nbr,
            cust_chngd_dt,
            cust_srce_sys_cd,
            subr_cust_seqno,
            subr_cust_id_nbr,
            subr_cust_srce_sys_cd,
            medl_rec_nbr,
            cust_home_phon_nbr,
            cust_home_fax_nbr,
            cust_home_emal_addr,
            cust_orig_efft_from_dt,
            cust_contus_cov_reas_cd,
            cust_contus_cov_efft_dt,
            cust_prfx_nm,
            cust_1st_nm,
            cust_mid_nm,
            cust_last_nm,
            cust_sufx_nm,
            cust_sex_cd,
            cust_ssn,
            cust_etncy_cd,
            cust_brth_dt,
            cust_dth_dt,
            cust_marl_stus_cd,
            cust_caus_of_dth_cd,
            cust_pl_of_dth_cd,
            cust_lang_cd,
            cust_home_phon_ext_nbr,
            cust_home_fax_ext_nbr
       FROM stage1.cust
      WHERE cust_seqno BETWEEN in_min_seqno AND in_max_seqno AND status_cd IS NULL);
 
UPDATE stg.cust
      SET status_cd = 'L'
      WHERE cust_seqno BETWEEN in_min_seqno AND in_max_seqno 
        AND status_cd IS NULL;
 
commit;

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:

Select all Open in new window

by: williampeckPosted on 2009-05-12 at 11:54:00ID: 24367994

Yes, I see what you are saying.

that's a really good point about a massive insert. But what about trapping errors? With the individual insert, we trap errors and write error records, see snippet.

  EXCEPTION
    WHEN dup_val_on_index THEN
      UTL_FILE.PUT_LINE(out_file, 'Duplicate record in CDR mem_memb for ODS SEQNO = ' || to_char(curr_seqno));
      
      UPDATE ods.mem_memb
        SET ods_stus_cd = 'D'
        WHERE memb_seqno = curr_seqno;
 
    WHEN no_parent_key THEN
      UTL_FILE.PUT_LINE(out_file, 'NO PARENT KEY ERROR IN CDR ' || tab_nam ||' for ODS SEQNO = ' || to_char(curr_seqno));
      UTL_FILE.PUT_LINE(out_file, sqlerrm);
      
      UPDATE ods.mem_memb
        SET ods_stus_cd = 'I'
        WHERE memb_seqno = curr_seqno;
 
    WHEN old_snapshot THEN
      UTL_FILE.PUT_LINE(out_file, 'SNAPSHOT TOO OLD ERROR IN ODS ' || tab_nam ||' FOR ODS SEQNO = ' || to_char(curr_seqno));
      UTL_FILE.PUT_LINE(out_file, sqlerrm);
      ROLLBACK;
 
    WHEN others THEN
      UTL_FILE.PUT_LINE(out_file, 'ERROR IN PROCEDURE MM_COPY FOR ODS SEQNO = ' || to_char(curr_seqno));
      UTL_FILE.PUT_LINE(out_file, sqlerrm);
      
      insert_err_tbl(curr_srce_sys_cd, curr_memb_id_nbr, curr_seqno, 'MEM_MEMB', sqlcode, '109');
      UPDATE ods.mem_memb
        SET ods_stus_cd = 'E'
        WHERE memb_seqno = curr_seqno;
 
      io_err := TRUE;

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:

Select all Open in new window

by: sdstuberPosted on 2009-05-12 at 16:03:55ID: 24370309

use automatic error logging to capture the errors.

first, create the error logs for each schema's cust table

EXECUTE DBMS_ERRLOG.CREATE_ERROR_LOG('CUST', 'CUST_ERRORS','STAGE_FINAL');

EXECUTE DBMS_ERRLOG.CREATE_ERROR_LOG('CUST', 'CUST_ERRORS','STAGE1');

then add the error logging lines to each sql

then you can either accept the errors and commit then log the exceptions
or rollback and log the exceptions or whatever you want.

INSERT INTO stage_final.cust(
                                 cust_seqno,
                                 cust_id_nbr,
                                 cust_chngd_dt,
                                 cust_srce_sys_cd,
                                 subr_cust_seqno,
                                 subr_cust_id_nbr,
                                 subr_cust_srce_sys_cd,
                                 medl_rec_nbr,
                                 cust_home_phon_nbr,
                                 cust_home_fax_nbr,
                                 cust_home_emal_addr,
                                 cust_orig_efft_from_dt,
                                 cust_contus_cov_reas_cd,
                                 cust_contus_cov_efft_dt,
                                 cust_prfx_nm,
                                 cust_1st_nm,
                                 cust_mid_nm,
                                 cust_last_nm,
                                 cust_sufx_nm,
                                 cust_sex_cd,
                                 cust_ssn,
                                 cust_etncy_cd,
                                 cust_brth_dt,
                                 cust_dth_dt,
                                 cust_marl_stus_cd,
                                 cust_caus_of_dth_cd,
                                 cust_pl_of_dth_cd,
                                 cust_lang_cd,
                                 cust_home_phon_ext_nbr,
                                 cust_home_fax_ext_nbr
           )
    (SELECT cust_seqno,
            cust_id_nbr,
            cust_chngd_dt,
            cust_srce_sys_cd,
            subr_cust_seqno,
            subr_cust_id_nbr,
            subr_cust_srce_sys_cd,
            medl_rec_nbr,
            cust_home_phon_nbr,
            cust_home_fax_nbr,
            cust_home_emal_addr,
            cust_orig_efft_from_dt,
            cust_contus_cov_reas_cd,
            cust_contus_cov_efft_dt,
            cust_prfx_nm,
            cust_1st_nm,
            cust_mid_nm,
            cust_last_nm,
            cust_sufx_nm,
            cust_sex_cd,
            cust_ssn,
            cust_etncy_cd,
            cust_brth_dt,
            cust_dth_dt,
            cust_marl_stus_cd,
            cust_caus_of_dth_cd,
            cust_pl_of_dth_cd,
            cust_lang_cd,
            cust_home_phon_ext_nbr,
            cust_home_fax_ext_nbr
       FROM stage1.cust
      WHERE cust_seqno BETWEEN in_min_seqno AND in_max_seqno AND status_cd IS NULL)
LOG ERRORS INTO stage_final.cust_errors;
 
UPDATE stg.cust
      SET status_cd = 'L'
      WHERE cust_seqno BETWEEN in_min_seqno AND in_max_seqno 
        AND status_cd IS NULL
LOG ERRORS INTO stage1.cust_errors;

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:

Select all Open in new window

by: williampeckPosted on 2009-05-28 at 13:49:59ID: 24497708

ststuber

(sorry for the delay)

good idea on capturing the errors while using a massive insert statement. it's something that I will have to work out in the future.

by: sdstuberPosted on 2009-05-28 at 13:51:34ID: 24497727

yes, automatic error logging is a fantastic feature that can give you a lot of versatility in how you do your data processing and exception handling

by: williampeckPosted on 2009-05-28 at 13:55:39ID: 24497760

Regarding my original question about increasing the commit size from 100 to 10,000, ststuber said:

>>decreasing the frequency of commits means you'll be consuming more rollback/undo in each transaction.

I didn't make it clear about the logic going on, but the reason I want to decrease the number of commits is that this will decrease the number of queries that occur.

With 4,000,000 rows and committing every 100 records, that's 40,000 times the cursor runs ! So I was thinking the better offset would be committing every 10,000 records so the cursor only runs 400 times, and the increase in overhead would be offset by the decrease in I/O running the cursor. What do you think ?

by: sdstuberPosted on 2009-05-28 at 14:56:45ID: 24498220

Do you mean this cursor?

FOR cust_rec IN cust_curs(min_seqno, max_seqno)
LOOP
...
END LOOP;

adding commits inside that loop does NOT make the cursor get re-executed.

The cursor will run one time only regardless of the number of commits

by: sdstuberPosted on 2009-06-26 at 05:31:23ID: 24720255

based on the author's comment "back to my original question"

24498220 answers that question, the cursor will only be queried once

I've also provided alternate solution to looping 24367433
and provided an option for potential error logging 24370309

So I suggest splitting between those three posts

20120131-EE-VQP-002

3 Ways to Join

30-Day Free Trial

For individual users
Instant access to solutions
Ask your tech questions
Start your 30-day Free Trial

Business Accounts

Perfect for organizations
Multiple users
Save over 36%
Create a Business Account

Answer for Membership

Earn free access
Showcase your knowledge
No credit card required
Sign Up to Answer

The Experts

98% positive feedback on 31,087 answers since March 2000. angeliii is a Microsoft Most Valuable Professional for his work with MS SQL Server & Develoment.

He has also proven his knowledge of Visual Basic Programming, PHP Scripting and Oracle Databases.

The Experts

97% positive feedback on 10,752 answers since July 2000. lrmoore has more than 18 years experience in the networking industry.

The six-time Mircosoft MVPs specialties include firewalls, virtual private networking, and network management.

Testimonials

"...and excellent source for support... Kind of like having your very own IT dept." Electriciansnet

Testimonials

"I was apprehensive at signing up at first. However... it has already made my life as an IT administrator much easier." JaCrews

Testimonials

"WOW! You guys have great, active, and knowledgeable people on here." moore50

Business Clients

In the Press

"If you’ve got a question... Experts Exchange can supply an answer.”

In the Press

"...an invaluable aid for both IT professionals and those who require tech support."

In the Press

"where IT professionals provide quick answers on just about any topic"

Business Account Plans

Loading Advertisement...

Question

Considerations for commit frequency in Oracle / Pl*Sql

Subscribe now for full access to Experts Exchange and get

Instant Access to this Solution

Oracle

PL*Sql

Oracle CRM

PL / SQL

Trusted by hundreds of thousands everyday for fast, accurate and reliable tech support.

See what Experts Exchange can do for you.

Got a question?

We've got the answer.

Need individual assistance?

Our experts are ready to help.

Want to learn from the best?

Read articles from industry experts.

Working on a long term project?

Store your work and research.

What Makes Experts Exchange Unique?

Trusted by the world's most respected brands.

Faithfully serving IT professionals since 1996.

Related Solutions

Free Tech Articles

Cloud Class Webinars

Join the Community

Give a Little. Get a Lot.

Answers

3 Ways to Join

The Experts

The Experts

Testimonials

Testimonials

Testimonials

Business Clients

Business Clients

In the Press

In the Press

In the Press