Viewing 15 posts - 31,261 through 31,275 (of 59,101 total)
johnitech.itech (2/1/2012)
:w00t:Hello i suggest you to use Using TRY...CATCH in Transact-SQL to avoid any undesired results
show below link
http://msdn.microsoft.com/en-us/library/ms179296.aspx
:hehe:
That's not likely to help with the privs necessary to write an error...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:54 pm
wiseman82 (2/2/2012)
I've never cared much for the new syntax, but you can also use:
Ditto that.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:41 pm
goodluck (2/2/2012)
We have clustered index on EOM_INT_Loan_nbr. The table has following 7 partitions in format as below...
All of that is well and good but only if the queries are based...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:38 pm
johnitech.itech (2/2/2012)
😛Just to say ,Sumanta Roy say the same answer from my sound ;-);-) Thank you for your reply quick quick quicklyy
What does that actually mean?
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:31 pm
svakka (2/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:23 pm
I have no idea and I think you're doing the right thing by working with DELL on this. Hopefully my response will also serve to "bump" your post back...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:14 pm
CELKO (2/2/2012)
If you want to get a running total, then use a VIEW with the new windows clause in the SQL Server 2012 release.
Really??? How'z he going to do that...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 2:03 pm
gugan_ta (2/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 1:50 pm
unnati.patel513 (2/3/2012)
Thank you very much..i got my answer
Ok... so what was the answer? Two way street here. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 1:44 pm
chrisvolny (2/3/2012)
What I want is to display the sum(decRebatableVolumeMTH) incrementally; like this. Hopefully, this makes sense.74611413711820249902252
74611413711820250900252
74831090801767149907867
7483109080176715090186272193
74831090991767149902292
74831090991767150908611588
7483180281767149905635
748318028176715090126188131
If you'd be kind enough to provide a "CREATE TABLE" statment and some 2005 compatible...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 1:39 pm
ssc_san (2/2/2012)
Got it Sean, Thanks!Thanks Dave!
Would you post your final solution, please? It may help others in the future. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 1:31 pm
johnitech.itech (2/5/2012)
Ok pls show m y below Link plsok check this link below
http://www.mssqltips.com/sqlservertip/2361/rebuilding-sql-server-indexes-using-the-online-option/%5B/url%5D
😉
The link doesn't work as is.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 1:22 pm
As a sidebar, I generally don't import directly from Excel spreadsheets because you can't tell when someone might have it open. I usually tell people to do an export...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 12:55 pm
sqlfriends (2/3/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 12:34 pm
This will do as you asked. Are you sure you want to delete items that only have a single instance like your original post seems to indicate where the...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2012 at 12:22 pm
Viewing 15 posts - 31,261 through 31,275 (of 59,101 total)