Viewing 15 posts - 55,906 through 55,920 (of 59,072 total)
Shrinking the log file causes fragmentation.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 7:34 pm
Very hard to say... people normally use cursors when they think there is no set-based option... normally they are wrong. Replacements will many times consist of the ill-conceived notion that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 7:30 pm
Like a couple of folks have asked already... post the rest of the code that uses the cursor and describe what the code is supposed to do. We're pretty good...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 6:23 am
Bill,
If YOU didn't know about the backups being taken, who does? Who's changing the tapes? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 6:16 am
Must be an echo, eh? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 6:14 am
Understood. Me? I export the data to a file and zip it so it won't be a duplication of data in the database.
Works kinda the same way with images... if a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 6:13 am
There may be some normal "healthy" blocking going on... you sure these are "deadlocks" (found in the SQL Server log) and not just blocking?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 5:51 am
Not in SQL Server 2000, you can't... this IS an SQL Server 2000 forum, ya know? ![]()
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 5:45 am
Sorry, Chris... lost track of this thread...
Specifically, what statement gave you that error?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 5:42 am
Just a suggestion...
When someone gives you an example... don't just take it at 100% face value... it's just an example. When someone suggests something new to you, like QUOTENAME, take a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 5:31 am
Use the SELECT to find out... doesn't matter how much time it takes... it's far better to know ahead of time than fixing "risky data" or having a large rollback...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 5:27 am
Heh
No... it is a tera-byte database with a lot going on, though. Web users, billing, invoicing, new customers, Dunning runs, 4 million + new CDR's...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2007 at 5:21 am
heh... you also bring up another great point... (maybe not intentionally)... If you do like you say with WHERE field <> '', it will inherently NOT find nulls because nulls...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2007 at 11:31 pm
Spot on, Vladan...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2007 at 11:15 pm
So you can't limit the query by level and tree branch on a single click?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2007 at 11:11 pm
Viewing 15 posts - 55,906 through 55,920 (of 59,072 total)