Database

CREATE SYNONYM [ schema_name_1. ] synonym_name FOR <object><br />
<br />
<object> :: =<br />
{<br />
    [ server_name.[ database_name ] . [ schema_name_2 ].| database_name . [ schema_name_2 ].| schema_name_2. ] object_name<br />
}<br />

USE tempdb;<br />
GO<br />
-- Create a synonym for the Product table in AdventureWorks2008R2.<br />
CREATE SYNONYM MyProduct<br />
FOR AdventureWorks2008R2.Production.Product;<br />
GO<br />
<br />
-- Query the Product table by using the synonym.<br />
USE tempdb;<br />
GO<br />
SELECT ProductID, Name <br />
FROM MyProduct<br />
WHERE ProductID < 5;<br />
GO<br />

smcnulty2000 wrote:

I'm curious enough to continue researching this but let us know if you decide on
a solution.

Mycroft Holmes wrote:

but we use Oracle for any really big data (multi TB)

Mycroft Holmes wrote:

our legacy systems were designed by incompetent, moronic, lazy, uneducated,
idiots who only had a vague idea about the business and absolutely no idea about
data structures

Mycroft Holmes wrote:

Still does not make sense to me. Why not take a copy of the procedures and run
them on the test server.

_Zorro_ wrote:

continuous integration with tfs 2010

_Zorro_ wrote:

I suppose your humans are better than ours

Mycroft Holmes wrote:

possibly we have simpler deployments

d@nish wrote:

This one: *****

<Property Name="ContactGUID" Type="uniqueidentifier">

<Property Name="SectionGUID" Type="uniqueidentifier" Nullable="false" StoreGeneratedPattern="Identity">

declare @generated_keys table(ContactGUID uniqueidentifier)
insert [dbo].[dtblContact](surname, forname)
   output inserted.ContactGUID into @generated_keys
   values ('Blog', 'Joe')
select t.ContactGUID
   from @generated_keys as g 
   join [dbo].dtblContact as t on g.ContactGUID = t.ContactGUID 
   where @@ROWCOUNT > 0

select  p.poke_id, s.[Name] as Poke_Giver_Name,s2.[Name] as Poke_Receiver_Name
from students s
inner join Poke p on p.Poke_Giver_Id = s.Student_Id
inner join students s2 on s2.Student_Id = p.Poke_Receiver_Id