If by live you mean production, not really, but this isn't because of an inherent limitation in VM. For production SQL Servers we go with big iron (clustered) and therefore...

If you need to pull the information into SQL Server, you can install MyODBC on the SQL Server and then created a linked server connection just as you would to...

We have used SQL Server on VMs in a non-production mode. We have also used SQL Server on VMs for disaster recovery testing. Speaking with a well-known company that does...

Standard is suitable for most folks. But there are a few differences around max capacity for memory/processors, # of nodes for clustering, options available for database mirroring, and other high...

In companies where you have split access, it's not unusual for password changes to be tracked on privileged accounts like those for domain, directory, server, and database administrators. Ideally there...

All true.

1. By Changing the password for SQL Server Startup account. By Default (and by the question this is the default installation) SQL Server installs on the user account, not...

True. And Full Text will have issues as well. In those cases you'd add NT Authority\SYSTEM as a login and grant it sysadmin rights.

To piggy-back on the others, go with where your experience is. That would be 70-229.

SQL Server 2000 does not have native encryption. You'll need to this outside of SQL Server or buy a third party product. Are you needing to store the password in...

The Windows Server 2003 SP1 fixes much of the MS DTC issues, but you can still have some crop up afterwards. Check for the latest COM+ Rollup Package and apply...

Take a look at the following article:

Free Encryption by Michael Coles

It covers his free toolkit which gives you the blowfish encryption protocol. You can use it through user-defined functions.

Best practices says that service accounts should change passwords according to the regular password policy employed by the institution (though no more than 90 days). But otherwise, I agree with...

I didn't catch this one when I proofread it. There is a difference in the operating systems. Windows 2000 Server cannot handle dynamic allocation of AWE memory in this manner....

You aren't able to allocate memory to individual databases. Memory allocation is at the instance level. You are, however, able to allocate memory to individual instances if you run multiple...

You can do backups with just the db_backupoperator fixed database role. This does not, however, give you the ability to do restores. The only way to restrict RESTORE permissions to...