Recent content by iamtechuser

ah yes sqlcmd!

Help Is OSQL compatible with 2005?? I am getting very messed up output in my file when I run OSQL on 2005... lots of blank lines and dashed lines. If I run on 2000, it's fine... what's the problem? Thanks

Duh, the WHERE IS NOT NULL clause is what I needed!! Now works great!!

So, here is the workaround: create table myTable(name varchar(20)) insert into myTable values ('Sue') insert into myTable values ('Joe') insert into myTable values (null) insert into myTable values ('Meg') insert into myTable values ('Ryan') DECLARE @myVar VARCHAR(100) SELECT @myVar =...

Although you do have a point about NULLs in the table... that does mess things up.

I'm sorry that isn't true... the problem is not multiple rows in the table not being able to be stored in the variable... it's the TEMP table I can do the select into the variable just fine with a regular table, and the @output formats the multiple rows beautifully... that what this is doing...

Thanks - I also had to restart agent, now works

backup purposes in addition to msdb backup

Hi, I am running the following stmts. insert into #tmp EXEC @result = master..xp_cmdshell @cmd SELECT @output = IsNull(@output + char(10) + result, result) FROM #tmp PRINT @output -- this is NULL!! SELECT * from #tmp -- this returns ROWS!! END I don't understand this... I believe it...

yeah, i use mps cuz i'm lazy... but they do have some limitations

Not using an Outlook profile, this is 2005 or am I confused? Don't recall ever having to do this on 2005 thx

Hi I need to select into a variable: insert into #tmp EXEC @result = master..xp_cmdshell @cmd IF (@result <> 0) -- return value from xp_cmdshell, 0 = success, 1 = failure BEGIN SELECT @output = result FROM #tmp But @output is empty... but #tmp is not. Help, how can I capture row data...

Thanks for the info :-) Have one more question, this is for 2005. When I query the sysjobs table using "select * from sysjobs" there is no originating_server column, only an originating_server_id column and it's "0" for all jobs. Doing a little poking around: (select distinct...

one more thing, though... while I can do this manually, I'm just wondering if there's a better way... can't help but wonder if I can automate this... afterall, it may be difficult to keep track of what's changed with many different developers, it would be very easy to overlook something... thanks

Is it possible to script maintenance plans?? thanks