Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
RIKIL
Starting Member
20 Posts |
 Posted - 2007-03-16 : 13:02:06
|
| Hello-I have an application that creates a lot of objects in the database. one thing that is useful is to know if any of the objects have changed since the product was installed or to be able to compare them to a known good state.What I was thinking of is a way to analyze each object (excluding the data in tables which change) to see if anything needs to be fixed.Is there a tool or something similar that already exists? I tried searching but am not sure I was using the right key words and didn't find anything.Thanks. |
|
|
Kristen
Test
22859 Posts |
Posted - 2007-03-16 : 13:09:58
|
| Do you mean something like Red Gate SQL Compare? That will compare the structure of two databases - e.g. one from a "previous version" and one from the "current version"SQL 2005 allows you to use Triggers to, e.g., Audit changes to DDLKristen |
 |
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2007-03-17 : 21:20:55
|
| Sounds like you have a problem your application design. Typically your database is static for any given version of an application (of course the actual data changes a lot).It also sounds like you have a problem with access, permissions and/or process if things change that you, or someone in a DBA type role, are not aware of.What makes you think that 'objects' in databases need to be fixed on a regular basis? I'm really curious to know what goes on in this application! |
|
|
|
RIKIL
Starting Member
20 Posts |
Posted - 2007-03-19 : 10:02:30
|
quote:
Originally posted by LoztInSpace
Sounds like you have a problem your application design. Typically your database is static for any given version of an application (of course the actual data changes a lot).It also sounds like you have a problem with access, permissions and/or process if things change that you, or someone in a DBA type role, are not aware of.What makes you think that 'objects' in databases need to be fixed on a regular basis? I'm really curious to know what goes on in this application!
we have several different products and each one that gets installed need to modify common views/objects in the database. Also, in this scenario tables need to have certain data and if I had a way to check this then problems would be easier to find. There are thousands of objects. |
|
|
|
LoztInSpace
Aged Yak Warrior
940 Posts |
Posted - 2007-03-19 : 23:43:57
|
| Nope. Still don't get it.If each product needs to modify something then those somethings are not really 'common'. Are you saying that you have, for example, a view always called "ABC" whos definition changes depending on what combination of products are installed?If this is the case then it's simply release management combined with security to prevent people fucking it up after install, but I think I still don't get what your problem is. |
|
|
|
RIKIL
Starting Member
20 Posts |
Posted - 2007-03-20 : 13:21:45
|
| Basically we have 7000+ objects in our database. When an upgrade happens we need to modify a lot of these objects, depending on the upgrade scenario. It is sometimes hard to make sure all of the needed changes happened and we often miss things. Its not just the static items like views ro stored procs but we also need to be able to verify data in tables (this should be static data). |
|
|
|
|
|
|
|
|
Database Integrity