Viewing 15 posts - 46,936 through 46,950 (of 59,095 total)
GilaMonster (11/29/2008)
Though, if you look, most of those certs are not SQL related...
True enough... but they are suppose to imply the ability to think and do a little research on...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 29, 2008 at 6:37 am
Jportelas (11/28/2008)
Seems like trying to cover all the failure scenarios is the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 8:48 pm
Heh... Read it? I wrote it! 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 8:40 pm
Dang... some of the things I forget... thanks Barry.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 7:31 pm
BWAA-HAA! And then, you double post the same question...
http://www.sqlservercentral.com/Forums/Topic610096-146-1.aspx
... you're not making a lot of friends here.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 6:41 pm
khushbu.kumar (11/28/2008)
GilaMonster (11/28/2008)
I'm not sure there's a good way in SQL 2005.Why can't you make the combination of the two columns unique?
I cant make combination as unique coz 1. abc...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 6:39 pm
tkoletsis (11/28/2008)
I think it's a very common case to import data from an excel file to sql server 2005 thru a stored procedure. There are many solutions solutions such as...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 6:34 pm
BWAAA-HAAA! New candidate for the Pork Chop Award... look at the question and then look at the certs this guy boasts in his signature...
http://www.sqlservercentral.com/Forums/Topic608903-360-1.aspx
... heh... guess all those certs...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 6:30 pm
Chris, I've created a Numbers table with the same column name as you (Number), and I cannot get the code to fail the same way as you have with the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 6:22 pm
Dang... I missed that... was looking at the wrong column for "dupes".
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 5:53 pm
CrazyMan (11/28/2008)
CREATE VIEW VTEST AS
SELECT A,B FROM TABLE1
UNION
SELECT A,B FROM TABLE2
This view cant do update :D, it is read only 🙂
Ummm... not if it's a partitioned view which IS...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 5:22 pm
homebrew01 (11/28/2008)
However, if I replace @list_Id with an actual value, then it shows an index seek.
Trick it...
WHERE l.List_ID > 0
AND l.List_ID = @list_id
AND...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 5:11 pm
Sorry... didn't see Gail's post on 1222...
I also share her concern on setting a deadlock priority... it's like asking a Mother which baby someone can kill. The best...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 4:48 pm
TNV (11/26/2008)
Basically I am new to this SQL Server stuff...
I am using MSSQL Server 2005 Express. I turned on trace by using DBCC TRACEON (1024). But in the errorlog,...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 4:46 pm
I tend to steer clear of using Table Variables... there's a whole lot of reasons for that but the biggest reason is that when in Query Analyzer or SMS for...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 28, 2008 at 4:44 pm
Viewing 15 posts - 46,936 through 46,950 (of 59,095 total)