Only the output parameters are listed, but if you look at the values at the end, there are 7, same as the number of parameters you have defined within the...

Not a problem. That's why we're all out...

SQL Swerver (4/22/2014)

---

We are struggling with this at the moment. We cannot utilise an Azure Private Network (APN) as the Azure SQL Database cannot be placed within it (we were...

yuvipoy (4/21/2014)

---

When i run the DBCC SHOWCONTIG() on my database it is displaying the attached list , is the tables got fragemented? if so how to resolve them?

most of my...

andrew gothard (4/22/2014)

---

I'm with all of them, and further than that I'd just install Michelle 'SQLFool' Ufford's maintenance script, configure any elements specific to your environment and largely forget about...

All the cloud services that I currently have (not...

SQL Swerver (4/22/2014)

---

Thanks Grant. That is helpful info even if it's a 'no'! 🙂

How would one configure the Azure SQL Database firewall to allow an Application hosted in Azure PaaS...

Use correct data types. If you need a floating point number, use a float. If you're expecting an integer, use one of the integer data types, not the float.

I'm with Yogeshwar Phull. Don't use show_contig any more. The dynamic management objects are so much better for this type of information.

Deadlocks are fundamentally a performance issue. So, are the other databases the same size as the one that's getting the issue? Are the same indexes in place? Are the statistics...

Here's the Books Online entry on DDL Triggers.

The thing I'd look to are the wait statistics. What's causing the system to slow down? That will tell you if you are stuck on I/O or if it's something...

I'm pretty sure there's no way to trace by JobId. But, you can trace by application name, so that will make it so you only ever get calls from SQL...

You can get a bunch of information from the backup files themselves, all through T-SQL. I've got an article on it over at Simple-Talk[/url].

Steve has largely nailed it. Be cautious using extended events to capture all statements though. That can be a ton of information.

Now, if you're running SQL Server 2014, you can...