So, not so much a bench marking tool as a load generation tool. HammerDB is one of the preferred approaches. But, if you want to simulate load, you could get...

Yes, they would be. It'd be a bad choice to do this after setting up a cluster. I'd suggest going the method of scripting everything for your initial deployment.

Yes, the role changes. When you fail over from one database to another within your availability group, the active node switches. If you're scheduling activities on the databases, you'll want...

And, as the article says, it's going to be a rare case. Don't panic. Read the KB. Apply the fix. It's probably not a bad idea to get ahold of...

Yeah, sorry, should have commented on that. The messages sound perfectly correct.

Could be a trigger? Nothing else is immediately coming to mind.

But if you're looking for backup, I'd strongly suggest using the built in backup mechanisms. Full backup, differential backup and log backups combined can ensure very little or even zero...

That almost sounds like a permissions issue on the script location. Just for an experiment, try placing it in the SQL Server \bin directory and see if you can execute...

You have to have the sqlps module if you're running this from standard PowerShell. Here's the topic on MSDN. I know you're calling it from SQL Server, but because you're...

jacksonandrew321 (11/25/2014)

GilaMonster (11/25/2014)

Considering that the article is completely wrong about index structure, I'd recommend not reading it.

Indexes are not binary...

In addition to just too much data, you can see this if you have extremely complex queries such as views that call views that join to views, etc.

Short answer, whatever...

The clustered index is the table. That's why it's a good idea to usually put the clustered index on the most often used path to the data. This is usually,...

And if you're on a 2008 server, consider using extended events to gather data instead of trace. It has better filtering and a reduced footprint.

And make sure you do some test restores to ensure you can get your database back and that you know how to use the log backups that you're taking.

Just make sure you set the maximum memory size within the SQL Server instance and then, as stated, let SQL Server do the memory management for you. For your memory...