Since you can't code 'USE @Dbname' you need to do something like this:

But when you do this, it still runs from within the master db.

You could modify...

Tami D (10/23/2007)

---

Thank you for the response. Unfortunately, I am using an output parameter and do not have the luxury of just excluding the column in the call to...

Even though I didn't have all the information, despite the number of rows, it's not a very big table. I did some experimentation. They shouldn't be hitting any issues assuming...

webrunner (10/23/2007)

---

Jereme Guenther (10/19/2007)

---

I don't know how or if you have time to read all of these posts, but here are my stats.

I obtained a BS in Software Engineering picking...

I set up a sample using these scripts:

CREATE TABLE BigTable

(

ID INT,

Date SMALLDATETIME,

[Value] decimal(18,10)

)

WITH x AS (SELECT 1000001 AS Id

,GETDATE() AS MyDate

,42.2 AS MyValue

UNION ALL

SELECT

ID + 1

,MyDate

,MyValue

FROM X

WHERE ID <...

I've never heard of anything like that. Best guess I can come up with (and it stinks) is to run spell check on the fields after you concatenate them...

That's good.

On which columns? Is it the PK? If not the PK, is it unique? What does the query plan that is taking 3 minutes look like and how...

All three of the Inside SQL Server 2005 books provide information you'll need.

Ignore my last post. It's utterly wrong.

What kind of indexes do you have on the table?

It is a security issue. You have to make that determination for yourself. It's off by default. Run sp_configure. It's the setting 'Remote Proc Trans' and setting it to 1...

What problems specifically are you worried about or experiencing?

54 million rows that are composed of one integer column just isn't going to be an issue. Are you experiecing fragementation of...

The issue you're running into is the logical processing order. The SELECT list is processed after the FROM, ON, JOIN, WHERE, GROUP BY, WITH, HAVING clauses. Any reference to items...

The variant doesn't scare me (much), but everything into one table? How many users are expected to access this? What does the indexing look like? Has anyone vetted the design...

Yeah, I mean, we had every single possible good technical, security and performance reason not to give them what they asked for. However, they trumped all those with a phone...