No, it would just be two data sources joined together via a lookup.

You need to find out what the processes are that are running on your SQL Server during the time when it is 100% (if possible). Use sp_who2 or...

sqldba_icon (1/26/2011)

---

I really always ask this question to my self. If there is a native tool like perfmon to capture all the data why do people spend $$$ on third...

SSIS seems to be as good an alternative to linked servers as anything, since you can have multiple datasets from differing sources.

Openrowset if you have to keep it...

Using your code as the base, the easiest way that I can think of to do this is using the Out-Datatable function that Chad Miller wrote and is out at...

I am not sure what you are asking, but you are right SSIS is not backwards compatible. That should not impact how you run a package through Powershell,...

I realize this is a couple of months out now but here is a good article for executing an SSIS package remotely via powershell.

http://blogs.msdn.com/b/dbrowne/archive/2010/10/11/remote-ssis-package-execution-with-powershell-2-0.aspx

Obviously you just end up calling dtexec...

We have been running on SP2 on our dev environments for about 2 months now and on our production environment for about a month and have not come across any...

I see what you are looking for here. I think the SMO route actually might be better for you then, and here is a link that describes how to...

First question is do you have a backup? If so, restore it run CheckDB and figure out where these 824 errors are coming from.

If you do not, here...

Determining the SQL Agent job information for a failed job is basically as easy as running a query against msdb.dbo.sysjobhistory where the run_status = 0 and then pulling out the...

In powershell you really don't exactly have to run the query against the server, since you have those properties available in different ways.

For instance, this script will go find your...

It is definitely a good idea to limit SQL at least a little when it comes to memory, because it will truly take every ounce that you give it and...

I just took your last DDL and replaced the final select with this

SELECT Distinct ROW_NUMBER() OVER(PARTITION BY re.AthleteGuid ORDER BY a.DateOfBirth DESC) AS rn,

r.Guid as RegistrationID

,a.Guid as AthleteID

,a.Firstname as FName

,a.LastName...

It is surprising that it would only return a few records and still cause you problems, but that does not make it impossible by any stretch. It depends...