GilaMonster (6/9/2015)

---

spaghettidba (6/9/2015)

---

GilaMonster (6/8/2015)

---

Well here's a new slant on the 'partitioning for performance'...

Switch the partitions that are needed out to a staging table, do processing on the staging table...

FootyRef (6/9/2015)

---

GilaMonster (6/9/2015)

---

FootyRef (6/9/2015)

---

So, I can't switch, say, four partitions out into a staging table, do inserts and updates against data in those partitions and switch them back into the...

GilaMonster (6/8/2015)

---

Well here's a new slant on the 'partitioning for performance'...

Switch the partitions that are needed out to a staging table, do processing on the staging table then switch...

You should identify which stats need updating rather than updating all the stats. You probably have some queries that perform poorly due to stats out of date and you should...

Alvin Ramard (6/8/2015)

---

spaghettidba (6/8/2015)

---

You don't need all the differentials since the last full, just the latest one.

This is what you need:

1. Last full backup

2. Last differential

3. All the log backups...

Duplicate post.

Replies here please: http://www.sqlservercentral.com/Forums/FindPost1692414.aspx

You don't need all the differentials since the last full, just the latest one.

This is what you need:

1. Last full backup

2. Last differential

3. All the log backups taken after the...

The first thing I would check is whether the logins enabled for the database are actually logging in or not. You can captur this event with Extended Events, as Grant...

This article should put you in the right direction: http://www.sqlservercentral.com/articles/Hierarchy/94040/

The most detailed and comprehensive article on this subject can be found on Erland Sommarskog's site: http://www.sommarskog.se/query-plan-mysteries.html

SQL Server instances are always active-passive in a failover cluster: the instance is active on one node and passive on all other nodes. Different instances can be active on one...

DECLARE @sampleData TABLE(

col1 VARCHAR(4)

, col2 VARCHAR(4)

, col3 VARCHAR(4)

, col4 VARCHAR(4)

, col5 VARCHAR(4)

, col6 VARCHAR(max)

);

INSERT INTO @sampleData VALUES ('abc.','def.','3fg.','59j.','567.','596040');

INSERT INTO @sampleData VALUES ('abc.','def.','3fg.','59j.','567.','596042');

INSERT INTO @sampleData VALUES ('abc.','def.','3fg.','59j.','567.','596043');

INSERT INTO...

I don't think it can be done in SQL Server.

I have a stored procedure that I use for this kind of task.

CREATE PROCEDURE [dba_formatQueryAsHTMLTable]

@query nvarchar(max),

@html nvarchar(max) OUTPUT,

@styles nvarchar(max) = NULL

AS

BEGIN

DECLARE @sql nvarchar(max);

DECLARE @header nvarchar(max);

DECLARE @body nvarchar(max);

IF...

As you have found out, nested tables are not supported in SQL Server.

You can use an XML column with a schema (typed XML).

Read more about it here: https://www.simple-talk.com/sql/learn-sql-server/introduction-to-xml-schema/

BTW,...