Foreign key constraints are currently implemented with special internal triggers. All of them are run FOR EACH ROW.
Note that these are implementation details that can change, so don't rely on it. But the basics have not changed over the last couple of major versions, so major changes are unlike...
> Full-text queries perform linguistic searches against text data in full-text indexes by operating on words and phrases based on rules of a particular language such as English or Japanese. Full-text queries can include simple words and phrases or multiple forms of a word or phras
@RoyiNamir he meant that you are using the english dictionary. Also, you really really need to do some research first. I mean, it's clear that you (as me too) just don't know enough about full text search on SQL Server to start implementing it
Ive been working on if for the last 8 hours. so I did a little research 9 as much as you can do in 8 hours). you can see it from my question is SO. also , in production environemnt - it does work. but when I created the FTS in my local computer - this is where I got stuck
@RoyiNamir I am talking having already read your SO question. The fact that it's a well asked question (I upvoted it), doesn't mean that it shows research about full text index. There's the fact that you didn't know it works with a dictionary, that the CONTAINS query you were using is meant for prefixes, etc. I don't mean this as an attack or anything like that
@RoyiNamir uhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh ... i'm not sure how any of this is working since you're not specifying unicode strings (though that may be implied in the FTS, but i dont think so)
Technically 2 weeks from now is when I get paid but I won't be transitioned until they can get a new ETL person in. That team is backlogged as hell and completely understaffed.
I got promoted another guy quit. 2 people are on a large project and 1 guy is on paternaty leave so all in all theres one guy left to handle requests.
@Lamak Technically, I merely explained what he said a little more in detail, but that still makes me a participant in the joke, of course. Especially since I probably confused you more than Bill did.
i'm in serious need of assistance. I have MS SQL Server 2005. When i pull up a site in the browser, let's say, www.abc123.com, it shows the site just fine. When i do a search in google for abc123 it shows me the site's link/url. If i click on it from there, then i'm redirected to a totally differ...
Looks like you're trying to run Java. Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet? Have you patched yet?
@AaronBertrand oh that one. yeah. that also gave me a sadface as well. it'd be really nice to have a live query statistics on anything that's currently running and not just something that's running with statistics
> This page has more animated GIFs than a Geocities page from 1995. That said, this is an exciting feature that keeps SSMS at the top of the client tools across all DBMS platforms.
> Load-balancing of read-intent connection requests is now supported across a set of read-only replicas. The previous behavior always directed connections to the first available read-only replica in the routing list. For more information, see Configure load-balancing across read-only replicas.
@PaulWhite pardon my ignorance ... so the big difference over against sys.dm_exec_query_memory_grants is going to be historical information on memory grants?
I suppose they would always be able to add new features quickly to the relatively new codebase that is columnstore and Hekaton, but it's still impressive.
Wasn't my down-vote, but might I offer a couple of suggestions: (1) You suggested NOLOCK and explained about two things that are important to you, but failed to warn any reader about much more important problems - hint: deadlocks & replication are not your biggest concerns (2) Being new to this site, please review this post and discard the expectation that you will always (or maybe ever) get any reasoning behind up-votes or down-votes. — Aaron Bertrand ♦2 mins ago
@PaulWhite whoa I hadn't even heard about that one - silly TAP saving some of the good news for the peons
(I'm finding that two things are increasing on our site: (1) SO-type questions and lots of spoon-feeding requests and (2) whining about down-votes.)