Nice joke.

Hopefully any of you that feel like that might get kick started to go do something more interesting with your life.

SQL Server isn't necessarily better at licensing on VMs, though I think you don't have to license more CPUs than you actually have.

You don't move an 8 proc box to...

you handle this in two ways.

1. You add the fix to v2 and either accelerate testing, or they wait for it to finish.

2. You make a change to v1, test...

I've never had good luck doing this. The script might work, but honestly, recreating them isn't that bad, even on dozens of instances and it's a one time task.

You should be using ALTER DATABASE to change the size and then restart SQL Server.

The older DBLib stuff might work (based on named pipes).

However you need some way to connect from Windows to Sybase, and once you have that, it's possible that you can...

You can do this multiple ways.

You can insert all the data from the restored tables, which may result in some duplicates if you don't have constraints to overwrite this.

You can...

Thanks for the update and glad it worked.

As an FYI, I don't recommend dump devices and would just back up to disk files. I'd use a different file name every...

I think what someone is asking is how many rows are in the table when you start (last week and this week).

Are you adding indexes later?

Could you be adding enough...

What's wrong? the older drivers from 2000 should work, although some of the newer features and keywords might not work.

How is the login that is having issues connecting to SQL Server? As a SQL login? It won't have Windows credentials to pass through the linked server.

There are not files within a .Bak file. There might be multiple backups stored within one file, but you cannot delete some of them now. You should back up to...

I'd set an view up on the linked server, select a, b, c from newserver.newdb.newtable, and then use the view for updates. That way you won't have to...

Not many people auditing, or maybe caring, ...

or maybe awake :hehe:

What version/edition of SQL Server is this?

It's got to be auto-close somewhere. Be sure you're not getting auto-close for another instance. Code might do it, but I can't imagine anyone...