i'm not a network expert, but if you have two different domains, the login mydomain\Lowell has no priviledges, and vice versa: the login yourdomain\AK1516 has no rights to anything on...

unless you have a trust set up between the two domains, you'll have to set up the linked server using a SQL login. you would not be able to pass...

note that even if the table with a billion rows had two columns, an ID and a varchar(30) for a name or something(38 bytes of data per row), you'd need...

RPSql (11/3/2010)

---

Select * from a table with one billion rows failing with following error (SQL 2005 SP3 HF11)

An error occurred while executing batch. Error message is: Exception of type 'System.OutOfMemoryException'...

what about this?:

you need to drop(or delete/truncate)

in the FK hierarchy...

there is a suite of views in the msdb database that you want to look at:

take a look at these:

select * from dbo.sysmail_allitems

select * from dbo.sysmail_faileditems

select * from dbo.sysmail_sentitems

select *...

both provide the ability to substitute a null for a known value, but COALESCE is overloaded with a param array,...

not enough info Laura; we'd really need the specific error that occurs to offer solid advice; what does "causes SSRS to shut down" mean to you? that that one report...

I saw you've been making the same request for a long time. I had shown you in another thread on the same issue an english number-to-words example that you could...

you can use a CASE to decide which value to insert:(note you said update, but it's really an insert in your example)

INSERT INTO dbo.myNewTable

SELECT

RTRIM(LTRIM('Art')),

RTRIM(LTRIM('Incidents')),...

an important piece of this puzzle is the account the SQL service is running under. Even though YOU...

don't declare one of the variables as varchar(max); use a defined size instead; no error occurs when you do this:

declare @bak_source varchar(255), @bak_dest varchar(255), @xcopycmd varchar(1000)

set @bak_source='"\\qa\d$\Full_2010.bak"'

set @bak_dest='"\\dev\d$\Data"'

set @xcopycmd='xcopy '+...

eek! SeanLange beat me to the punch on this one! you got some payback on that one, way to go Sean.

Nope; that's a limitation of a CTE; it can be used only for one statement.

if you get rid of the pseudocode, and show us what you are actually doing, we...

lol happens way to often lately!

type faster! i guess it's a race now.