Viewing 15 posts - 4,126 through 4,140 (of 10,144 total)
ringovski (8/18/2013)
ChrisM@Work (8/16/2013)
Stefan_G (8/16/2013)
thava (8/15/2013)
...
This is a good idea - scan the large tables a single time.
To improve performance even more you should include a WHERE condition for GNLFSMID as...
August 19, 2013 at 3:15 am
Yes - have a read of this MS article.
August 19, 2013 at 1:40 am
adonetok (8/16/2013)
This will delete entire row.What I need is to delete data in [ORDERDATE] cell and keep bbb in [NAME] field.
An UPDATE then.
update mytable set date = NULL where name...
August 16, 2013 at 7:15 am
delete from mytable where name = somename and date = somedate.
August 16, 2013 at 7:06 am
pwalter83 (8/16/2013)
ChrisM@Work (7/24/2013)
pwalter83 (7/24/2013)
ChrisM@Work (7/24/2013)
Lowell has already asked but the question remains unanswered: why do you want to hold the same data in two places at once?
Hi,
The reason is -...
August 16, 2013 at 6:59 am
I think it should look more like this:
SELECT
w.eID, w.name,
al.[status],
COALESCE(al.CheckTime, c.[Date]) AS [Date]
,CASE WHEN al.CheckTime IS NULL THEN 'A' ELSE 'P' END AS Attendance
FROM dbo.employee AS w
CROSS JOIN...
August 16, 2013 at 6:51 am
immaduddinahmed (8/16/2013)
...actulay this work is above my level thats why i am getting complexity 🙂
You're doing just fine - you've learned a huge amount in the time you've been posting...
August 16, 2013 at 5:57 am
My mistake, coding before thinking. Try this:
SELECT *
FROM Calendar c
CROSS JOIN employee e
LEFT JOIN attendlog a
ON a.eid = e.eid
AND a.CheckTIme = c.Date
WHERE c.[Date] >= CAST('20130801' AS DATETIME)
AND...
August 16, 2013 at 5:34 am
immaduddinahmed (8/15/2013)
from attendlog aleft outer join employee e on a.eid = e.eid
If an employee has no attendance record for the selected time period then they will be excluded...
August 16, 2013 at 4:39 am
As Stefan has pointed out, your spec is full of errors and is very difficult to understand. What I suggest you do is to show with examples what you mean...
August 16, 2013 at 4:14 am
I'd use a CROSS APPLY cascade. This article [/url]has at least one example which is very similar to your requirements.
August 16, 2013 at 3:23 am
Stefan_G (8/16/2013)
thava (8/15/2013)
...
This is a good idea - scan the large tables a single time.
To improve performance even more you should include a WHERE condition for GNLFSMID as well:
WHERE ...
August 16, 2013 at 3:02 am
I'd guess that's way too complicated for the optimiser to deal with and you've got a plan which is far from ideal. Thava has the right idea - you should...
August 16, 2013 at 1:31 am
The performance would be appalling. Consider Luis' approach, or even APPLY():
SELECT SalesPersonID, FirstName, LastName,
x.Address1,
x.Address2,
x.City,
...etc....
FROM dbo.SalesPersons
OUTER APPLY (
SELECT Address1, Address2, City
FROM dbo.Addresses
WHERE (LookUpID = 1)
AND (RecordTypeID = 3)
)...
August 15, 2013 at 9:25 am
;WITH src AS
(
SELECT
database_id, db_buffer_pages = COUNT_BIG(*)
FROM sys.dm_os_buffer_descriptors
--WHERE database_id BETWEEN 5 AND 32766
GROUP BY database_id
)
INSERT INTO MyNewTable ([db_name], db_buffer_pages, db_buffer_MB, db_buffer_percent)
SELECT
[db_name] = CASE [database_id] WHEN 32767
THEN 'Resource DB'
ELSE...
August 15, 2013 at 9:19 am
Viewing 15 posts - 4,126 through 4,140 (of 10,144 total)