I am guessing you are just trying to import the Datasource for AdventureWorksDW into an SSAS project, so here is one of the MSDN tutorials that walks you through how...

I doubt that this is related but it sounds similar enough that I figure I may as well share. We had an issue where the statistics were out of...

I do something very similar but slightly different where I build a comma separated string for the filenames before doing the ReceiveFiles command. I did not come up with...

I believe you are very close here you just need to save the changes (so to speak).

I think this will get it for you.

[System.Reflection.Assembly]::LoadWithPartialName(’Microsoft.SqlServer.SMO’) | Out-Null

$smo = New-Object (’Microsoft.SqlServer.Management.Smo.Server’) "Server\Instance"

$jobstodisable=...

I can see the value in having a sysmoddate and a sysadddate however, I think in most cases having an auto-incrementing id is probably still a good thing if for...

We actually had a situation very similar to this where we would receive different results based on the MAXDOP being greater than 1. It also turned out that...

In this case I am not passing in the credentials (note that I am using a trusted connection). But you can, here is the help file information that shows...

If I am understanding your request correctly, if you were running this from server AB you would run something like

update b

set b.id = a.key

from dbnamea.dbo.b b

join OPENROWSET('SQLNCLI', 'Server=servercd;Trusted_Connection=yes;', 'SELECT...

select * from master.sys.servers where is_linked = 1

will give you a list of the linked servers currently on your server.

Using SQLCLR would be a situation where you would have some .Net code that created a connection that you could dynamically pass into a function or proc that would make...

Note, that when you do this you do have to prefix the proc with "sp_". Here is a good article to describe that.

http://www.mssqltips.com/tip.asp?tip=1612

It occurs to me that your issue may be as simple as just making your proc a system object (so that it can run under any context without problem).

You should...

I see what you mean. The problem here is not how you are calling the proc (it is most assuredly running against every database), the problem is that there...

Name the SearchAllTables proc sp_SearchAllTables, load it into the master database and then run

exec sp_msforeachdb 'use ? exec sp_SearchAllTables ''searchstringhere'''

That should run it against each of the databases on your...

Within the Job Properties you can change the Step Type to SQL Server Integration Services Package and you can select your package that is stored in MSDB that way. ...