We havent used it much. When it first came out it was handy since we could do some testing on the server that was running SQL 7 in production, I...

If you're using the SA account to connect to distributor or subscriber you'll have to change them. Need to check both logreader and distribution agent jobs, plus the linked server...

Not at all. You have to differentiate user access in the application, vs the permissions the application needs to run. You certainly can provide each user with a sql login/password,...

You could update sysdatabases, you'll have to allow updates.

Andy

http://www.sqlservercentral.com/columnists/awarren/

There's no connection really. Just to be clear, even though you're authenticating the user you can add NT groups and grant the permissions to the group (which you should really...

Not directly - you can fake it by writing the status to a table or a file, have the next step check it for the status.

Andy

http://www.sqlservercentral.com/columnists/awarren/

I'll have to admit not testing this completely, but I have moved db's fron an AWE server to one that is not. I would expect the only difference is how...

You can generate script for it from Enterprise Manager, or via the object browser in QA in SQL2K.

Andy

http://www.sqlservercentral.com/columnists/awarren/

I normally use alter, though more often I version by creating a new version of the proc that includes the change. For those cases when it's a minor tweak to...

No reason you can't do both. Safeguard the data using NT authentication, but you can add code to the app that requires a password - one scenario might be you...

SQL Server supports set rowcount, the older way of doing Top N. Other than that, maybe a cursor that will loop x times and insert the keys in a table,...

I cant give many details yet, but we'll be publishing an e-book soon that will address a lot of that I think. Stay tuned!

Andy

http://www.sqlservercentral.com/columnists/awarren/

Hard to say what is normal. Build the indexes you need, kill the ones you dont. If that means index size is bigger than the table, so what? I'll try...

SQL backups are secured by disk permissions. Same for RAID. Keep the tapes secured - usually are in a locked server room anyway.

Andy

http://www.sqlservercentral.com/columnists/awarren/

Processor time will increase if you have increased activity due to page swapping. Which goes back to more memory, more stuff to swap to disk. Shouldnt be hard to try...