Viewing 15 posts - 53,386 through 53,400 (of 59,098 total)
high hit volume GUI = very high volume OLTP 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 5:35 am
The script that Minaz points out is for the data... not the table schema.
There is no way to audit changes/modifications to a table's schema in SQL Server 2000 through the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 5:33 am
!! DIR C:\Temp
Not real sure I'm happy about THAT working because the following also works...
!! DEL C:\Temp\some file name
Great article of tips, Steve... thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 5:26 am
Now that would be a good reason... can't see it making much of a difference in non-looping batch code, but I can see where it could make a heck of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 5:14 am
Sure and understood... but, with proper indexing, good set based code, and the like, access will be extremely fast without having to go through a cache layer that needs to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 5:04 am
I still need to see how you're calling the proc because that might be part of your problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 4:45 am
Heh... then there's shops like what I used to work for... I'd not only be the DBA, but I was also the OS guy, the guy that built the computer,...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 4:43 am
Understood... but the interviewer from Microsoft asked why it's better to list all of the columns than to use Select *...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 4:39 am
What would really be "cool" is Low Temperature Differential Stirling Engines. Design one that would work at 70-90oFd Diiferential (would be kinda large but light-weight) that would kick out...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 27, 2007 at 4:37 am
Yep... maybe that too. Same thing goes with statistics, I suppose.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 8:17 pm
It just seems very odd to me that you want a DBA to drive your very expensive truck but you won't even let him/her check the pressure in the tires...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 7:39 pm
What are you using to call the proc? In other words, let's see the EXEC statement 'cause the code in the proc is mostly correct. Only thing wrong...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 7:23 pm
Heh... to many conversions and concatenation for me... the following does the trick as well...
SELECT STUFF(CONVERT(VARCHAR(30),GETDATE(),107),1,3,DATENAME(mm,GETDATE()))
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:54 pm
The best answer would be "to protect the results". I've seen it happen before... DBA's can decide there's a problem with a table or they need to instantiate some...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:48 pm
Thanks for the feedback! Good to know that it wasn't BCP.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 26, 2007 at 4:36 pm
Viewing 15 posts - 53,386 through 53,400 (of 59,098 total)