Brandie Tarvin (7/24/2015)

---

So everyone at work is thrilled with me right now for solving a slow-running report issue when I discovered 4 table scans (of the same table) in a...

Congratulations!

Prior to 2012 the options for this were replication and log-shipping. As you read up on Availability Groups I think you'll find that they are probably the best way...

Can you share? It looks like you just didn't double-up the single quotes within your string, but I want to be sure.

I don't think the machine id is there, but you can get the user and I'd assume that SharePoint is running under a unique service account. You do this...

Please lookup AlwaysOn Availablity Groups using your favorite search engine. All of this is documented in multiple places including BOL. This site also has nice set of articles...

I'd start by making all my string variables NVARCHAR to make sure that isn't the problem.

In addition to what Luis has said, foreign keys also ensure that no rows can be inserted into the "data" table without a corresponding row in the lookup tables. ...

If you are really on SQL Server 2014 or even 2012, I'd recommend an AlwaysOn Availability group with a synchronous read-only secondary.

Can you post the query or a generic representation of it?

Cross server queries, whether using Linked Servers or openrowset are notorious for performance issues depending on how you...

Sounds like you either have a faulty controller connecting to the drives or needs a firmware upgrade based on the error. I have no experience with Lenovo Flex systems...

Because SQL is a declarative language you can't enforce which criteria is evaluated first, the optimizer chooses based on what it thinks will work fastest. The other thing you...

Are there any scheduled jobs (windows, backups, etc...) running at 12:30? Any information in the event logs around that time?

What is the data type of the column you are excluding? If it is a LOB type (XML, NVARCHAR(MAX), etc...) including/excluding the column can have a large impact on...

You don't need both, but you can enable both without doing any harm. Did you restart the SQL Server service after making the change?