The wide index is less efficient in terms of storage, but in terms of covering, it'll be the same. Either an index has all the columns needed to satisfy a...

I'm honestly not sure. It sounds like something was cached at the client of the other session. Recompiling the procedure from the first session would invalidate the execution plan in...

At the end of the backup process, any transactions that have completed while the backup was running will be brought into the backup. The recovery step of the restore process...

I'd suggest taking a look at the Minion scripts[/url] by the Midnight DBA team. That gives you a lot more control than the maintenance plans.

First, the server has to be part of a failover cluster (the service, not the physical set up). Then you go to Configuration Manager to enable availability groups. This is...

Think of each database as a service. A given service has a contract that says for these inputs, you get these outputs. With that in mind, any given access mechanism...

My query performance tuning book also talks about the dangers of multi-statement table valued user defined functions. The newest one has the most discussion around that.

If you don't have experience in development overall, then I'd suggest following the suggestions in the post above. If you're trying to understand how to run the debugger within T-SQL,...

It depends. One thing that the optimizer takes into account is foreign key constraints. Since you can't have those across databases,...

Regardless of what you do to modify the backup, and I like the suggestions, make darned sure you test the restore to ensure you both know how to do...

zahid.nawaz (11/12/2014)

2) What effect it has if we have one cluster index but many none cluster indexes? according to following blog it can even create extra performance problems instead of...

If you're working within SQL Server, I wouldn't worry that much about product specific T-SQL. The vast majority of applications developed stay within the RDBMS that they're developed within. So,...

Because it's so very easy to undo stored procedure encryption, it's really a waste of time. Why do you think you need to encrypt your procs?

Not a correction, an enhancement.

Unclear how many transactions you're dealing with. That can still affect your choices. Is the system going to be OLTP or Reporting focused? That's also going to affect how it...