linked-server

I am trying to create a linked server in SQL Server: --Create the link to server "uranium" EXEC master.dbo.sp_addlinkedserver @server = N'uranium', @srvproduct=N'', @provider=N'SQLNCLI' --Add the catch-all login with SQL Server authentication EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'uranium', @useself=N'False', @locallogin=NULL, @rmtuser=N'BatteryStaple', @rmtpassword='Horsecorrect' And it creates fine. But any attempt to query the linked server, e.g.: SELECT * FROM uranium.Periodic.dbo.Users results in Msg 18456, Level 14, State 1, Line 1 Login failed for user 'BatteryStaple'.

I am developing an app where i have a local database in SQL Server Express. During work in local database, we need to execute a query on another SQL Server / live server and its return a value and with this value we execute a query in local server. It is OK when executing this query against 2 or 3 queries, but i have around 5000 records on which I need to execute same process. I have done with above style but its take too much time. I've found that we can run a query on multiple servers. Can i run a query on SQL Server Express and server at same time and and run my whole queries in this style?

I have the linked server set up in SQL Server 2008. But I could not run any query against the linked server. I tried to run this simple command but it's not working SELECT * FROM MYSERVER..ALANH.TEMP_UPDATE1 This is the error I got when I run the above command. Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "OraOLEDB.Oracle" for linked server "MYSERVER" reported an error. The provider did not give any information about the error. Msg 7312, Level 16, State 1, Line 1 Invalid use of schema or catalog for OLE DB provider "OraOLEDB.Oracle" for linked server "MYSERVER". A four-part name was

New to the tSQLt world (great tool set) and encountered a minor issue with a stored procedure I am setting up a test for. If I for some reason have a stored procedure which connects to mutiple databases or even multiple SQL servers (Linked Servers). Is it possible to do unit tests with tSQLt in such a scenario? I commented already, but I would like to add some more. So as I said already, that you can do anything that fits into the single transaction. But for your case I would suggest to create synonyms for every cross database/instance object and then use synonyms everywhere. I've created