06.18.05
ConceptDraw
Project
 Project
management application ConceptDraw Project will make your
plans come true! Use ConceptDraw Project to organize and
manage projects with clear, attractive Gantt charts, WBS
charts and MindMaps. Share your projects across Mac and Windows. Intuitive and versatile, it gives you you simple way to create clear, nice-looking project plans in minutes.
Features:
Manage Multiple Projects
Efficient planning and management of multiple projects
Share Tasks and Resources
Track and report projects on Windows and Mac OS X
For more information
/ download |
|
 |
|
|
|
Todays
Featured Article:
How To Attain SQL Server High Availability
By: Brad M. McGehee
You may find it hard to believe, but it is possible to maintain SQL Server high availability and not spend a fortune. In fact, you can spend a fortune and still not get SQL Server high availability. Sound like a paradox? Not really. SQL Server high availability is not a direct function of how much you spend. Instead, high availability is more about what you do right and what you do wrong.
Before we get too far along in our discussion on how to achieve high availability at minimal cost, let's first take a brief look at what high availability really is. Let's assume we live in a perfect world where nothing ever goes wrong. In this case, our SQL Servers would be available 100% of the time they are needed by users. This might be 24/7, or 8/5, depending on your user base and how your SQL Servers are used. In other words, there is a time frame where SQL Server needs to be up and running efficiently, and as long as they are up and running efficiently during that time frame, then you have 100% availability.
But what does "up" mean? Does it mean that the SQL Server service is running, even if it is running so slowly that users can't get their work done on a timely basis? Or does it mean that the SQL Server service is running and that users can access it on a timely basis? I think most DBAs would assume the second option. If users can't access SQL Server on a timely basis, then SQL Server is not really "up".
Read
the rest of this article |
|
|
|
|
|
|
|
|
|
|
