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 |
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
 Posted - 2005-12-29 : 04:13:38
|
| How can I determine an index creation date?RegardsSachinDon't sit back because of failure. It will come back to check if you still available. -- Binu |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-12-29 : 14:17:32
|
The sysindexes table doesn't have a "crdate" column, like most of the other SYS tables, so I reckon there is a fair chance that "you can't"  You could have your own "copy-table" of sysindexes and compare it against sysindexes periodically, and store any differences - together with a date/time - so that you have an audit. And you can probably use SQL Profiler to record Index Create operations ... but that may be answering the wrong question!Kristen |
 |
|
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
Posted - 2005-12-29 : 23:05:27
|
| oh :(.Thanks anyways Kristen.RegardsSachinDon't sit back because of failure. It will come back to check if you still available. -- Binu |
|
|
|
madhivanan
Premature Yak Congratulator
22864 Posts |
Posted - 2005-12-30 : 00:17:27
|
| orYou need to manually document the changes you are doingMadhivananFailing to plan is Planning to fail |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-12-30 : 14:03:19
|
What you been smoking Maddy?  Now then ... you and I know that both of us, and sachinsamuel, always document our changes, but its the other blighters we've got to worry about!Kristen |
|
|
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
Posted - 2005-12-30 : 14:43:48
|
Better we should. In my case somebdy has created an index on a computed column. Because of which all my jobs are failing and also some storedprocedure. For them I have to explicitly set ARITHABORT ON. I also tried changing the value of arithabort on on dboption but it didnt worked. Finally I had to explicitly write ARITHABORT ON on all my jobs. They all are working but I just wanted to check where is my cheese? I know when the index was created as I can see in my job history that it was working fine till last week but dont know how to identify the one which got created. Got my leasson  . Hope you and Madhi agree with me.RegardsSachinDon't sit back because of failure. It will come back to check if you still available. -- Binu |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-12-30 : 17:14:26
|
| Sounds like an index on a view then. I hate them - for specifically the reason you have identified.We've had to rename a perfectly good Sproc to be "MySproc_V2" and replace it with:CREATE PROCEDURE MySprocASSET ARTIH_ABORT ONEXEC MySproc_V2just to work around the problem, because, for whatever reason, we've been unable to persuade ADO that SET ARTIH_ABORT ON can be accomplished at the client end Kristen |
|
|
|
sachinsamuel
Constraint Violating Yak Guru
383 Posts |
Posted - 2005-12-30 : 17:46:05
|
| No I don't have indexed view. It's the problem with index made on computed column. And thats the reason I want to know all the index made on that date. I also did the same thing, I had to alter the store procedure with SET ARITHABORT ON. And the other major problem was my job failed which used to do DBCC CHECKDB.So I used below 2 lines on the top of my job and it worked.SET ARITHABORT ON SET QUOTED_IDENTIFIER ON Just wanted to share all my experience.RegardsSachinDon't sit back because of failure. It will come back to check if you still available. -- Binu |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-12-31 : 10:53:59
|
| "Just wanted to share all my experience"Glad that worked for you, it wasn't sufficient for me to include that in the SProc, hence I had to make a wrapper with that and EXEC the SProc from there - so that "ARITHABORT ON" was "active" at the time the Sproc was called, rather than being activated during the execution of the SProc itself. Bit of a PITA Kristen |
|
|
|
|
|
|
|
|
Index Creation Date?