Another reason might be the way you actually query the data.

Instead of going three levels deep in your xml query I'd rather use CROSS APPLY (as recommended in the other...

The concept is called "CrossTab". A related article is referenced in my signature. For a dynamic number of columns please see the DynamicCrossTab article...

DECLARE @master-2 TABLE(mf1 CHAR(2),mf2 INT,mf3 INT,mf4 VARCHAR(30),mf5...

Please have a look at Jeff Moden's "Running Total" article[/url].

I think it's the best performing apporach. But you need to understand the requirements in order to get consistent results....

Jeff Moden (5/10/2010)

---

As much as I love working with the Tally table, it just doesn't need to be that complicated for this. In fact, the CASE formula in the...

Please provide the table definition (DDL script), some sample data (INSERT ...SELECT), your expected output related to the sample data, what you've tried so far and where you get stuck.

For...

Glad I could help 😀

Here's a slightly different apporach (using the sample data Cory set up):

I prefer STUFF over SUBSTRING for scenarios like this since it's a little less coding and it doesn't include...

You might want to have a look at the Tally table article referenced in my signature. There is a split string function included you could modify to meet your requirements.

This...

duplicate post.

Discussion already started here

Ok, here's how I'd do it:

DECLARE @tbl TABLE

(

UserID INT ,

Email NVARCHAR(50) ,

Pass NVARCHAR(20) ,

FirstName NVARCHAR(20) ,

LastName NVARCHAR(40) ,

DisplayName NVARCHAR(50) ,

PROFILE NVARCHAR(MAX) ,

DisplayEmail NVARCHAR(50) ,

CellPhone NVARCHAR(20) ,

UpdatedBy INT ,

UpdateDate DATETIME ,

Deleted...

I wonder how you actually can provide really fast SAAS solutions without having a Tally table available 😀

Would be interesting to have a small talk with your admin...

One thing...

Would you please provide some sample data to play with?

Basically, a sample xml file with the structure you're faced with holding FAKE data and your target table with a few,...

Store the shredded xml data into a relational (temp) staging table.

Use this table and check for existing emails within your insert statement.

You would nee to provide an ORDER BY clause based on a column that will hold any order criteria.

Since SQL Server does not perform a row-by-row processing, it will select...

Did you have the time to read the articles I mentioned...