If you're using RDP, network isn't an issue.

Stats should move, but as Jeff mentioned, they often don't seem to in a backup/restore.

Setting password to not expire is a bad idea. They ought to be changed periodically.

I've done this two ways. Note that this was relatively low volume, but it worked in each case.

1. We process the order and load into the DB. Meaning everything is...

I've edited your code. You highlight it and then click the " on the left to format it.

What you should do is not "execute" the code, but do the print...

Robert,

Is that true? In that case, security is being bypassed for single user mode. That's a big hole. If you don't have rights, you shouldn't be able to connect in...

It is easy to paste in, and honestly I'm not sure that I'd do it for this reason. However I do think that this is an interesting idea, and it...

I think the answer is highly dependent on options, which makes it a poor question. It could appear to be one way or the other in many tests, until you...

It's an auditing message. You must have a setting enabled to log failed logins and the instance is logging them. It means that someone attempted to log on with an...

I like Lowell's idea. The problem with snapshots is they don't survive restores or issues with the system. They also would not survive a migration to another server. IMHO, archiving...

If you don't have a windows account with administrative access, I suggest you find the media for SQL Server and perform an uninstall/reinstall.

In terms of hacking an old database, how would they know the record count? What if it was a dev database? I've seen those before, development passwords moving to production...

I don't think we know what you mean. There are different types of writes for different things. What are you trying to learn or what are you working on?

You ought to check on a few things, like the counts for these SELECTs (without the inserts), and also on the execution plan. My guess would be you are getting...

Note that the log is restarted when the logs are cycled or SQL is restarted. That can be a long interval, and the logs can be big. So they can...

When you use SSMS, you can use the "Script" button to get the T-SQL script that is run. Then you can schedule that as needed.