network profile
| bio | website | summitsystemsinc.com |
|---|---|---|
| location | Cookeville, TN | |
| age | 29 | |
| visits | member for | 1 year, 7 months |
| seen | Jan 14 at 4:13 | |
| stats | profile views | 6 |
I'm a software developer (B.S. CmpE) in the manufacturing sector. My primary development language is Java, but I also support legacy applications written in VB6 and Foxpro 6.
|
Nov 27 |
awarded | Supporter |
|
Dec 16 |
comment |
“SELECT TOP N” returns the wrong results I don't understand why step 1 of the backup job exists. It does not appear to be redirecting the output of dbcc checkdb anywhere. Assuming it found a problem during the nightly job, would it continue on with the backups? |
|
Dec 16 |
comment |
“SELECT TOP N” returns the wrong results I have not run dbcc checkdb, but I did find a nightly job defined on the server which the DB owners had apparently created. Step 1 runs DBCC CHECKDB ('DB Name') WITH NO_INFOMSGS on every database on the server. Step 2 does a full backup on every database. |
|
Oct 24 |
comment |
“SELECT TOP N” returns the wrong results I'm not able to run dbcc checkdb yet. I don't own the database, so there's a bit of red tape involved in letting me perform maintenance tasks on it. |
|
Oct 24 |
comment |
“SELECT TOP N” returns the wrong results The query is used directly by my application. It is not used as a subquery, view, derived table, etc. We have used it many times a day for several years and have heard of no such problems until very recently. As such, I believe this problem is rooted in something environmental, and I am almost certain the database has not received proper maintenance in a very, very long time (if ever). |
|
Oct 24 |
comment |
“SELECT TOP N” returns the wrong results Not yet. I'm a developer, not a DBA, and I'm coming at this from a standpoint of explaining why the system I wrote on top of the database is suddenly screwed up. This database is several years old. I helped develop it, but was never granted the authority to maintain it. I sincerely doubt that a competent DBA ever got anywhere near it. My boss looked at the execution plan for this query and found that the index used by it was 100% fragmented. We have made no code changes related to the query since before it messed up, so I thought it might be related to indexes. |
|
Oct 22 |
awarded | Student |
|
Oct 21 |
awarded | Autobiographer |
|
Oct 21 |
asked | “SELECT TOP N” returns the wrong results |
