Viewing 15 posts - 49,096 through 49,110 (of 59,102 total)
If you want the object ID from the name, why not just use...
SELECT OBJECT_ID('objectnamehere')
There are several system functions that will help keep you from redeveloping the wheel... just look them...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 11:36 pm
Ummm... let's do a small test on the "bad" machine... if you open a "Command Prompt" window, type DIR and press {Enter}, does it return anything? And, no, not...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 8:47 pm
If transactional replication does not replicate truncations, then there is no need to audit inserts to rebuild a truncated table because you can always get it back from the replicated...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 8:36 pm
Ah... I get it now... you want to test/compare every combination of 1 to 10 characters (36 characters total) of the old UDF against the new UDF. (3611)-1 is...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 8:33 pm
Thanks for the feedback...
By the way, being a bit of a code formatting and documentation freak, I really like your tagline on your posts. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 7:52 pm
rbarryyoung (7/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 7:04 pm
Lester Policarpio (7/21/2008)
I want to ask how to troubleshoot this kind of problem. I'm handling many servers everyday (select, update, delete). I created...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:34 pm
It may be operating off a bad cached plan... try the WITH RECOMPILE option in the stored procedure. It could also be "parameter sniffing"... lot's of articles available for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:20 pm
Lynn Pettis (7/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:16 pm
That scenario (like many) audits the wrong thing... you should only Audit the DELETED table... the current value is always in the original table.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 7:49 am
GSquared (7/23/2008)
you need the original data, or you can't track what was changed in the first update on a column.
??? I'm not sure why you say that! We...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 7:28 am
GilaMonster (7/23/2008)
On my main system, TempDB is 6 files of 8 GB each.
Now THAT sounds like a fun system to be on and that the DBA (you, Gail?) might...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:48 am
Ross McMicken (7/23/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:45 am
Jonathan Kehayias (7/23/2008)
Unless there is some amazingly complex operation happening that we haven't seen the code for, then this is misplaced.
Heh... I think about 99% of all CLR code is...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:39 am
Heh... 50MB for a TempDB... we start our TempbDB up at 12 Gig!
--Jeff Moden
Change is inevitable... Change for the better is not.
July 23, 2008 at 6:16 am
Viewing 15 posts - 49,096 through 49,110 (of 59,102 total)