Viewing 15 posts - 32,311 through 32,325 (of 59,099 total)
Cadavre (10/10/2011)
Rakesh.Chaudhary (10/10/2011)
just for faste performance and for learning purposes
Well, golly gosh! It seems that after you went to all the trouble of reading the link in my previous post,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2011 at 5:08 am
Rakesh.Chaudhary (10/10/2011)
I want to use while loop for this..............DECLARE Total_salary CURSOR
FOR
SELECT
e.Emp_Id,FirstName,(Basic+HRA+Allowance)AS Total_Salary
from Salary Inner Join Emp_Detail e
on e.Emp_ID=Salary.Emp_Id
OPEN Total_salary
FETCH NEXT FROM Total_salary
WHILE @@FETCH_STATUS=0
BEGIN
FETCH NEXT FROM Total_salary
END
CLOSE Total_salary
DEALLOCATE Total_salary
The only difference...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 10, 2011 at 5:07 am
Very interesting. Thanks, Johan. Have you tested it for performance at all? And, yes... I'll check out the link you provided.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 7:38 pm
Gosh... we just got you out of one looping problem. 😛 What does the store procedure you want to loop-over actually do?
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 7:34 pm
Jakub Dvorak (10/7/2011)
I wrote exactly same query in the meantime. Only thing I would change for metioned large datasets is adding WHERE clause to last update which filters...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 7:25 pm
oradbguru (10/8/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 7:01 pm
Ok, David... I've seen quite enough and you've asked for it 😉
You write nicely, you cite references, you write code to build test data and then to do the tests,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:58 pm
meghna.bhargav (10/9/2011)
I want to design universal schema in database where any end user can dump any type of data into database coming from any type of source for e.g. excel,...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:50 pm
Tom,
Take a look at the following article so you can understand how "J Livingston SQL's" method works... it' quite effective.
http://www.sqlservercentral.com/articles/T-SQL/63681/
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:45 pm
J Livingston SQL (10/9/2011)
pls note ...date range vailidity needs scrutiny
comments in code
USE [tempdb] --- a safe place
GO
--== condtionally drop table...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:42 pm
ALZDBA (10/9/2011)
SSC has some nice articles to get you started with both.
For powershell this...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:22 pm
We recently had a similar problem at work and, of course, everyone jumped in on the ISNULL bandwagon as a resolution... and, as some expected, the code took comparatively forever...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:14 pm
Something else you need to be aware of that some of us found out while testing code in one of my articles... certain collations will make your server run horribly...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 6:03 pm
opc.three (10/7/2011)
Please, have a look at PowerShell. Once you ramp up you will never want to open CmdShell again.
Well I might especially if it's to fire off PowerShell from a...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 5:47 pm
For those interested in what some of the more cryptic designations for ASCII characters less than character 32 are, please see the following link...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 9, 2011 at 4:39 pm
Viewing 15 posts - 32,311 through 32,325 (of 59,099 total)