Brett Veenstra's questions

We run numerous scheduled jobs using MS SQL 2005 job scheduler.

Over the past few weeks, we've been witnessing that a running job will simply STOP and will not record any history in the Log File Viewer.

What appears to be happening is that the server will start a job and record these steps into msdb. At a random step during a job, the server will stop running the job and it records no error. This silent failure prevents a "Step 0" record from being created and we won't see anything in the Log File Viewer.

Anyone else experience this?

When migrating servers, how can I easily script all my SQL Server Jobs onto a new machine?

NOTE

Not accepting "backup msdb" as the answer.

I used to have need for OSXVNC (now Vine), but with Mac OSX Leopard, I'm quite happy with the built-in VNC support.

I just am wondering how I go about uninstall this thing though. When I fire up Console app, I see OSXVNC is maintaining a log, so I assume a Daemon's running. This should be easy picking's for all Mac sysadmins.

I realize the Vista trick of typing cmd then SHIFT+CLICK+END from the Search menu gets you a privileged terminal session.

Has anyone found the necessary tweaks to turn this capability into RIGHT+CLICK folder convenience?

I'm trying to connect via SQL Server Powershell Cmdlet (read not ADO.NET) using SQL-based Authentication, not Windows Integrated security.

Anyone know the format to use for this?

• Server: foo
• Instance: DEFAULT
• UserID: homer
• Password: simponsrock

Edit:
I can get to this SQL-cmdlet path using SQL Server Management Studio.

When doing it that way, the path is:
SQLSERVER:\SQL\foo\DEFAULT+homer

The problem is that I cannot set-location to this path via PowerShell

I tried creating an ultimate setup for my powershell environment.

I created "Microsoft.PowerShell_profiles.ps1" with a bunch of statements to setup my default profile.

When I start a PowerShell session though, I get:

File C:\Documents and Settings\xxx\My Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be loaded. The file C:\Documents and Settings\xxx\My Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 is not digitally signed. The script will not execute on the system.

In 64-bit Windows versions, is there a way I can tell if an executable requires 64-bit to launch?

I'm looking for a better way than Process Explorer to find out, preferrably BEFORE launching.

EDIT: So how would I know that an application requires Win64 environment?

I want to take an existing VMWare virtual machine and run it in VirtualBox 2.2+. Is there any utility to do this?

We had a server rename/migration and I was using the Offline Files feature on Windows XP SP2.

Every so often, my "Offline Files Status" icon appears in my Taskbar and let's me know that the old server is "Offline: Unavailable to reconnect".

I have since pointed the Offline files to the new server, however my Offline Files still seems "attached" to the old server for some reason.

When I look in the "Offline Files Folder" on my PC, there is NO reference to the old server, so it must be stuck somewhere.

How do I get this corrected?

What is the most compelling reason to flash your router to the DD-WRT firmware?