Viewing 15 posts - 31 through 45 (of 310 total)
Stored procedures give you :
Performance
Maintainability (You are only passing parameters - not trying to work out how a lengthy command was constructed)
Modularity (the n-tier thing)
Security - you can restrict access...
June 5, 2007 at 1:52 am
Also not analysed it in detail but what jumps at me is that you are using a cursor. Cursors are slow slow slow !!! You should be able to use...
May 31, 2007 at 1:47 am
I doubt that there are many IT projects of any size that can be deemed a complete success in all respects. There is always something that could have been done...
May 1, 2007 at 1:47 am
Any software development project - any project in fact - is a team process. The whole team owns it and the whole team succeeds or fails together. If there is...
April 30, 2007 at 1:50 am
Dates is dates !!! Chars are for display only. Trying to process dates as strings is asking for trouble (because of the formatting issues David mentioned) and inefficient. SQL Server...
April 23, 2007 at 1:50 am
I would always put readability and maintainability first - any rules are a means to an end, not the end in themselves. As a general principle though, avoid reserved words!
April 17, 2007 at 1:29 am
Hope you did it but, if not, you must uninstall all CTP components before installing SQL Express.
April 12, 2007 at 1:42 am
Thank you, Hugo - an excellent explanation. I usually just update fields that I have changed and check those but the single field test is, as you say, more efficient.
April 5, 2007 at 2:04 am
What I never have understood is ... what on earth practical USE is it?
April 5, 2007 at 1:27 am
I would dispute the 'correct' answer specified. MSDN says 'Every time that a row with a timestamp column is modified or inserted, the incremented database timestamp value is inserted in...
April 4, 2007 at 1:45 am
Thanks for that. Some of the affected files are different versions. The trick now is to find the correct ones for an unsupported OS !
March 28, 2007 at 8:15 am
Use a GROUP BY instead of distinct. Then you can avoid duplicates with something like :
SELECT ID, [Name], MIN(SequenceField) FROM dbo.MyTable GROUP BY ID, [Name]
... but, as everyone says, you MUST...
March 27, 2007 at 2:31 am
.. and I'm thinking you're right Jeff ! I didn't mean to imply anything otherwise.
As long as EmpID is unique (presumably it is) and that is the selection order required...
March 20, 2007 at 6:54 am
Remember that SQLServer does not guarantee any physical row order - the execution plan may change as data changes and lead to a different order in the result set unless...
March 20, 2007 at 2:42 am
Viewing 15 posts - 31 through 45 (of 310 total)