Viewing 15 posts - 34,666 through 34,680 (of 59,102 total)
mtillman-921105 (3/11/2011)
Also, you should rewrite the query to use an INNER JOIN rather than the older way its using more than one table.
There's no performance gain in it. The...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 10:41 pm
Eric M Russell (3/11/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 5:06 pm
Lowell (3/11/2011)
--using Stefan's setup:
/*--Results
(No column name)(No column name)
1172.24
322.25
3223.25
*/
SELECT Count(IPAddress),parsename(IPAddress,4) + '.' + parsename(IPAddress,3)
FROM #tempIPTable
Group By parsename(IPAddress,4) + '.' +...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 4:50 pm
ltwitchell (3/11/2011)
I usually have called myself the data janitor. Makes people laugh and disarms them a bit from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 4:44 pm
Jason-299789 (3/11/2011)
JeffA unique contraint would elimate the chance that there are 2 or more records with the same EmpId.
Exactly!. And THAT is precisely what is required for a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 11:51 am
You don't need that function. SQL Server already has such a function. Try the following code and see.
SELECT DATENAME(mm,GETDATE())
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 9:52 am
JunkIt (3/11/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 9:29 am
In the meantime, yes... import their data into a table and do a FULL OUTER join between your table and theirs. Things with NULL on one side or the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 7:28 am
You probably don't need SSIS for this. Look into BULK INSERT which will do the job on a thousand rows in less than a second.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 7:25 am
Take a look at the first link in my signature line below. It may be why it's taking so long for someone to help you.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 7:22 am
ranganathanmca (3/10/2011)
Table structure :
create table tbemployee(
empid varchar(1200,
Name varchar(220),
supervisor_id varchar(120)
)
we need get the employee levels
Example:
--1
---2
----3
-----4
Like this...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 6:58 am
M Joomun (3/11/2011)
Jeff Moden (3/10/2011)
Before you even think of capturing only the changes and the columns names, very carefully consider how you...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 6:54 am
Ok... thanks, ZA.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 6:41 am
Jay Hopping (3/8/2011)
.... well, at least...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 6:10 am
The alternative is good but it's still ok to use the CTE... I just dump it's results into a TempTable if I need to call it more than once so...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 11, 2011 at 6:05 am
Viewing 15 posts - 34,666 through 34,680 (of 59,102 total)