xSQL Object 2.5.3.6
xSQL Object is a professional grade SQL Server tool for comparing and synchronizing SQL Server databases. It allows the SQL Server developers and database administrators to keep their development, testing and production environments in sync with minimal effort. Some of the features include: 1) Full support for SQL Server 2000 and SQL Server 2005 - all objects; 2) Cross version comparison - compare a SQL Server 2000 database with a SQL Server 2005 database and generate version specific change scripts; 3) Schema snapshots - maintain a history (audit trail) of the schema changes and provide for safe and efficient reversing of schema changes when necessary; 4) Wide array of options allows for granular control of the behavior of the comparison engine; 5) Enhanced object filtering - compare and synchronize only the objects you want; 6) Comparison results displayed in an easy to read color coded grid that allows the user to drill down into the differences, view the scripts of objects, filter results and more; 7) Generate safe, standardized change scripts and review scripts before executing on the target database; 8) Command line utility provides for scheduled, unattended comparison and synchronization operations; 9) Enhanced scripting capability - script any object or the whole database, script schema only or schema and data together.
How can xSQL Object help you?
For the independent .NET / SQL Server developer: while you are pounding code on your machine you are liberally making small changes in the local database – add a column here, change a width there, add a view, make a change to a stored procedure and so on. At some point in the early morning hours as the World wakes up you are ready to publish your work on the production server, somewhere across the continent – just a few clicks and the early risers will see your masterpiece (application) in action. Well, not so fast unfortunately, all those small changes you made to the local database must be made to the production database otherwise your application is not going to work – now, that is some painful and tedious work to say the least. And here is a twist to make this a real nightmarish scenario – remember last week when the client needed those urgent changes and you were forced to do the “unthinkable” – make changes right on the production database! Worst yet, you realize that you forgot to bring those changes down to your local, development database – no words can describe the pain you must feel at that moment! Is this time for panic? No it is not, it is time for xSQL Object – in just a few clicks it will show you exactly where the differences are on both sides and better yet auto-generate the scripts that you need to quickly and safely make the changes. Download it now and see the difference – you have two weeks to use it on any size database and you have forever free to use it on smaller size databases.
For the member of a .NET / SQL Server development team: your DBA has “stapled” the database change rules on your forehead. You have to follow the protocol, thoroughly document the changes you are requesting, write the change scripts as well as the scripts for reversing those changes if need be. When all is ready submit the request to the DBA and keep your fingers crossed. Hopefully you did not miss anything because if you did you are in trouble – the QA team will find out and changes will be rolled back and the process will be delayed and you will be held responsible for the project delay! Even if you did not miss anything the DBA may determine that the change scripts you submitted do not follow the standards and reject them. Hours upon hours of valuable time are consumed by such tedious tasks that a developer would rather not deal with. Well, you don’t have to – xSQL Object automates the process and makes the task quick and enjoyable. You will never miss a change again, the change scripts will be standardized, well formed every time and you will be on the good side of your DBA. Download it now and see the difference – you have two weeks to use it on any size database and you have forever free to use it on smaller size databases.
For the SQL Server DBA: we all know you are the king of your enterprise – nothing can happen without your approval, no executive decision can overwrite your rules and decisions as no one would dare take that responsibility. Now, that is one of the great things on the life of a DBA, however with the great power vested on you comes great responsibility. The database you control is the heart of any modern organization - if it malfunctions the enterprise will be put at a great risk. You must be meticulous, establish strict rules for managing the database and carefully control and monitor any schema changes - keep track and be able to reverse changes at a moment’s notice. On top of all this you have to deal with those hard to discipline developers that are not following the strict guidelines you have put in place – you have to review change scripts written by this diverse group of developers each of them with his/her unique “style” of coding. Wouldn’t it be nice if you could effortlessly maintain a complete history of schema changes and be able to point exactly what changes happened when? Wouldn’t it be nice if you could schedule a job that runs periodically and tells you whenever something changes? Wouldn’t it be great if you could automatically generate scripts that are inherently safe? You can get those and more with xSQL Object and xSQL Command Line Utility. Download it now and see the difference – you have two weeks to use it on any size database and you have forever free to use it on smaller size databases.
How can xSQL Object help you?
For the independent .NET / SQL Server developer: while you are pounding code on your machine you are liberally making small changes in the local database – add a column here, change a width there, add a view, make a change to a stored procedure and so on. At some point in the early morning hours as the World wakes up you are ready to publish your work on the production server, somewhere across the continent – just a few clicks and the early risers will see your masterpiece (application) in action. Well, not so fast unfortunately, all those small changes you made to the local database must be made to the production database otherwise your application is not going to work – now, that is some painful and tedious work to say the least. And here is a twist to make this a real nightmarish scenario – remember last week when the client needed those urgent changes and you were forced to do the “unthinkable” – make changes right on the production database! Worst yet, you realize that you forgot to bring those changes down to your local, development database – no words can describe the pain you must feel at that moment! Is this time for panic? No it is not, it is time for xSQL Object – in just a few clicks it will show you exactly where the differences are on both sides and better yet auto-generate the scripts that you need to quickly and safely make the changes. Download it now and see the difference – you have two weeks to use it on any size database and you have forever free to use it on smaller size databases.
For the member of a .NET / SQL Server development team: your DBA has “stapled” the database change rules on your forehead. You have to follow the protocol, thoroughly document the changes you are requesting, write the change scripts as well as the scripts for reversing those changes if need be. When all is ready submit the request to the DBA and keep your fingers crossed. Hopefully you did not miss anything because if you did you are in trouble – the QA team will find out and changes will be rolled back and the process will be delayed and you will be held responsible for the project delay! Even if you did not miss anything the DBA may determine that the change scripts you submitted do not follow the standards and reject them. Hours upon hours of valuable time are consumed by such tedious tasks that a developer would rather not deal with. Well, you don’t have to – xSQL Object automates the process and makes the task quick and enjoyable. You will never miss a change again, the change scripts will be standardized, well formed every time and you will be on the good side of your DBA. Download it now and see the difference – you have two weeks to use it on any size database and you have forever free to use it on smaller size databases.
For the SQL Server DBA: we all know you are the king of your enterprise – nothing can happen without your approval, no executive decision can overwrite your rules and decisions as no one would dare take that responsibility. Now, that is one of the great things on the life of a DBA, however with the great power vested on you comes great responsibility. The database you control is the heart of any modern organization - if it malfunctions the enterprise will be put at a great risk. You must be meticulous, establish strict rules for managing the database and carefully control and monitor any schema changes - keep track and be able to reverse changes at a moment’s notice. On top of all this you have to deal with those hard to discipline developers that are not following the strict guidelines you have put in place – you have to review change scripts written by this diverse group of developers each of them with his/her unique “style” of coding. Wouldn’t it be nice if you could effortlessly maintain a complete history of schema changes and be able to point exactly what changes happened when? Wouldn’t it be nice if you could schedule a job that runs periodically and tells you whenever something changes? Wouldn’t it be great if you could automatically generate scripts that are inherently safe? You can get those and more with xSQL Object and xSQL Command Line Utility. Download it now and see the difference – you have two weeks to use it on any size database and you have forever free to use it on smaller size databases.
No comments:
Post a Comment