Openrowset()

http://msdn.microsoft.com/en-us/library/ms190312.aspx

Or xp_cmdshell then bcp the table over to server x.

Both commands need to be enabled though

Create a non clustered index on emptype.

Create table #emptype (id int identity(1,1), emptype varchar(20), empid_eg int)

Insert into #emptype

Select distinct emptype, null from tablename

Update #emptype

Select empid_eg = max(a.empid)

from #emptype...

Forget renaming them and instead create 3 new dns aliases (cname records)

Join the table to itself using row_number or some other unique id on id =id+1 (ie next row) where datediff a and b less than 14.

It depends what you want to see in the summary. If just a small table with number of rows transferred, I would just generate a html table with results...

You have missed the queryout option before the filename after the ". Look at example F here: http://msdn.microsoft.com/en-us/library/ms162802.aspx

Thanks for posting the article, but I don't see any benefit to these options. Ctrl-t opens templates which are more useful than snippets and exist since 2005, and surround...

I understand that the answer works, but can someone explain the process for it?

Is it:

Join the original table with a derived table, using CASE to swap the values (which occurs...

Shared cpu cycles and overcommitted RAM allocations, complete loss of control over system performance, licencing issues, and possibility of failed backups in which the blame falls on the dba.., server...

I would restore norecovery, then log restores until ready. If you move the db's individually, you risk having problems if there are links between the db's. Also...

Why does select i+1, char(i+1), isnumeric(char(i+1)) from l where i < 127 need an i+1 in each column?

Does the CTE with UNION ALL increment i? It needs to increment in each column? I no comprehende

add the user to the database role "db_datareader" and "db_datawriter. Then grant execute all or grant execute on specific stored procedures if they use them. Or grant db_owner...

Could also be the security settings on the linked server. Try getting the trigger to run under a specified user context by using:

EXECUTE AS LOGIN = 'blah'

UPDATE table...

This works fine for me. I was able to replicate your issue by removing the 'connect' user rights on the master db for the remote login specified in the...