Viewing 15 posts - 23,761 through 23,775 (of 59,102 total)
The title of this post is different but it's a duplicate post. No replies here, please. Please see the other post already in progress at the following URL.
http://www.sqlservercentral.com/Forums/Topic1565517-373-1.aspx
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 2:53 pm
Michael Valentine Jones (4/28/2014)
Not being able to have identity columns and foreign key constraints looks like a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 2:50 pm
Actually, since this is for INSERTs, consider putting a default on the Last_Updated column along with a NOT NULL constraint and you won't even need a trigger.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 8:44 am
For something like this, consider and "INSTEAD OF" trigger for the inserts. That way, you're only hitting the table once. Updating after the fact will prove to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 8:43 am
ahmed_elbarbary.2010 (4/28/2014)
suppose i want to calculate payroll every month for employees...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 8:40 am
Brandie Tarvin (4/28/2014)
Come to the Dark Side. We have cookies!
Heh... Mongo like cookies! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 8:31 am
Just a thought...
The looping is going to cause a full table scan of a 100 Million row table for each and every loop. That's a shedload of I/O that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 8:30 am
Eirikur Eiriksson (4/8/2014)
hisakimatama (4/8/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2014 at 7:55 pm
Wow! Great question. Books Online specifically identifies what will occur with LOBs during a REORGANIZE but says nothing specific about LOBs during REBUILDs. It does say that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2014 at 7:41 pm
hunchback (4/8/2014)
Try:
SELECT
*
FROM
#employee
WHERE
Surname LIKE '%[^0-9a-zA-Z][^0-9a-zA-Z]%'
OR GivenName LIKE '%[^0-9a-zA-Z][^0-9a-zA-Z]%';
GO
Heh... simplicity at it's best. The only...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2014 at 4:53 pm
Crud post on my part... took it down. :blush:
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2014 at 4:45 pm
priestxandar (4/27/2014)
Thanks for trying to help me, i read those articles you send me, but i cant figure out how to use the info inside to help my self....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2014 at 1:40 pm
If it were me, I'd break the Parent and Child values up as true parent and child values and set them into an Adjacency list, something like this but missing...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2014 at 12:24 am
spaghettidba (4/26/2014)
yuvipoy (4/25/2014)
Say i am having 10 master tables.
Can i create tables each one on 10 secondary files(.ndf) in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2014 at 11:49 pm
Paul White (4/14/2014)
Jeff Moden (4/14/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2014 at 12:19 pm
Viewing 15 posts - 23,761 through 23,775 (of 59,102 total)