Viewing 15 posts - 47,956 through 47,970 (of 59,095 total)
Want a better answer faster? Take a look at the link in my signature below and also post the query you already have. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2008 at 1:25 pm
Jeez... doesn't anyone know how to use "Get External Data" on a simple view anymore? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2008 at 1:12 pm
Ummm.... if you make a "sandbox" database, it won't get overwritten. The key is having access to the production data via a "reporting" database... if you create synonyms or...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2008 at 12:16 pm
Heh... no... writing smart code isn't difficult. You simply have to make the choice not to write bad code. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2008 at 11:31 am
Heh... it's customary to test your own test code before you post it to make sure it works. Anyway, since there seems to be a pattern to things...
--===== If...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 11:12 pm
I agree... it depends. If it's CRUD, it should probably be done in separate procs. If it's to merge data from a staging table into a final table,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:55 pm
vidhyasudha (9/12/2007)
Hi There,
Im having the problem when i tried to update the value in the column.
My table has following columns,
ID Degree
C111 BSC
C111 MSC
ID acts as a Primary Key
I need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:34 pm
By the way, Ainsley... SQL Server doesn't support multi column updates using a list of targets vs a list of sources separated by a single "=" sign. You have...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:30 pm
Actually, there is a direct replacement for RowNum=1 in SQL Server... it's called TOP 1. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:25 pm
Cross post... please don't answer on this thread... go to the following instead...
http://www.sqlservercentral.com/Forums/Topic580370-1291-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:22 pm
Still, the deed is done and the OP is gonna whack the internal documentation in someone's DB. Questions like this should simply go unanswered. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:14 pm
Franco_1 (10/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:05 pm
And, yet, we so no testing nor references to Microsoft articles on the subject... does anyone have proof one way or the other? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 8:01 pm
jlp3630 (10/3/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 7:51 pm
jeremiah.peschka (10/3/2008)
Likewise, CLR functions have an even larger performance advantage over T-SQL functions for complex computation, string manipulation, and business logic.
With the exception of RegExReplace, many of us have been...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 3, 2008 at 7:48 pm
Viewing 15 posts - 47,956 through 47,970 (of 59,095 total)