djacobsen 84059 (6/29/2011)

---

I'm not sure if I should create it's own topic, but I see this was recently answered (a rarity when you stumble upon a post from a search...

ChacMoll (6/29/2011)

---

I was reading an article from MSDN which says that a stored procedure created with managed code can run on a client computer, I've been looking for several sites...

In your estimation is Page Splits/Sec at all useful to look at within an overall picture (e.g. combined with other perf indicators/counters, et al.) for looking into adjusting index fill...

Try this please and see what happens:

create proc openrowset4

as

begin

if 1=0 -- no-op

...

drew.allen (6/29/2011)

---

opc.three (6/29/2011)

---

UNION ALL used how it was just shown in your post (as a 2005-compliant row constructor equivalent to VALUES() ) will allow you to use the APPLY technique...

Eric M Russell (6/29/2011)

---

TravisDBA (6/29/2011)

---

opc.three (6/28/2011)

---

I am curious...I am not sure what you mean. Maybe it would help if I...

PortQry has worked well for me in the past:

http://support.microsoft.com/kb/832919

As I understand it (not an expert at backup/restore) you cannot restore a secondary filegroup unless the primary has already been restored. If you need this sequence regularly I would...

The two usages of UNION ALL you're comparing a VERY different.

UNION ALL used how it was shown earlier in the thread will cause multiple scans of the data.

UNION ALL used...

USE database_name

GO

SELECT *

FROM sys.objects

WHERE USER_NAME(OBJECTPROPERTY(OBJECT_ID, 'ownerid')) = 'the_owner_name' ;

GO

Pam Brisjar (6/28/2011)

---

Basic situation:

We need to get data from DB2 into SQL Server. We do this via OPENQUERY and an SSIS data flow task.

However, I'd like to parametrize the...

Phil Parkin (6/28/2011)

---

You could try returning the columns from a stored proc and using that as the source for your data.

You'll need to include a dummy select as the first...

Itzik has it down, use the APPLY operator for this. UNION ALL will scan the data multiple times, APPLY will only scan it once, and it's cleaner than the CROSS...

Here is your query rewritten using ANSI-92 JOINS:

SELECT t1.id,

t1.col1,

t1.col2,

...

I strongly second that forsqlserver!