Are you able to change this from snapshot replication to transactional, this way only the initial snapshot would take some time and then only new transactions will be passed over...

Slipstreaming is doing a SQL 2008 install that also installs SP1 during the install, not the usual post install of the service pack, Windows 2008R2 will not install SQL 2008...

You could also use dos query user query user via xp_cmdshell and punt the output into a table and then parse this out to find rdp sessions.

Andrew

Did you do a slipstream install, if not you will need to, the slipstream install SQL SP1 as part of the install, windows 2008 R2 requires this and MS has...

You could create an ssis package and try and connect, if it does not respond the step fails and you then have an on fail step to insert into a...

A nice free tool for this is http://www.idera.com/Products/Free-Tools/SQL-permissions/ You run it before the restores on you dev\qa\stage box to get the permissions, it also scripts out the logins,...

Is this being done through Management Studio, if so, are you able to script out the change and see what is occurring, is the change creating drop and recreation and...

I used to use logparser from MS (you can search for its use on this forum) and this worked fine, but although you can build a query to limit what...

I know in SQL 2008 if you don't add a windows login\group during install you can get locked out if you don't configure a SQL login, the builtin administrators group...

What is the change you are trying to implement, are you scripting it or running it through management studio?

Andrew

If I remember rightly, to connect to SQL 2008 using MMS 2005 you need the client tools patched up to SP3, doesn't answer the original question, but my two cents.

andrew

Had another look and it is returned via select suser_sname(owner_sid) from msdb.dbo.sysjobs, not as complicated as I thought.

Andrew

Try using sqlcmnd or the earlier cmd line tools

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

Andrew

I have a feeling it is returned via a dll, sp_helpjob ends up calling xp_sqlagent_enum_jobs which in turn calls xpstar.dll, can't see what that does, but I wouldn't be surprised...

If it is 2005+ you should be able to use the schema changes history report, it tells you when and who made database change, it does not tell you what...