If you need to change the data in your local database, you have no choice but to use the full backup.

However, daily restores seems like a lot. Think about whether...

You don't want the file to grow by itself, ever. That's an emergency thing if you can't respond.

You should be monitoring this and if you see it getting low, add...

Not sure what you mean about the stored procedure in the table.

You don't need the name of the stored procedure to call it, you can send in parameters in order....

This has happened at times in 2000, and as mentioned above, the only thing to do is stop and restart SQL Server.

I would not link the servers. Often people with rights to query staging do not have rights to production (nor should they). It's a potential security hole.

Instead I'd give rights...

I hadn't mentioned writing, but it is something I'd ask for if it's an unusual request. Thanks for mentioning and glad that people are thinking of it. I'd also note...

I think there are always jobs. I've seen reports this week that IT hiring was strong in the US and also that it was not doing well. Overall you can...

I'd use Karthik's solution and then be sure you get them into a version control system. Ideally you are checking them out of some SCC and then editing them before...

Constraints internal to the table require scripting. If there are FKs to other tables, are you importing them?

Andras mentions scripting it out, probably the easiest way, recreate the table in...

I don't know of any software like this for end -users. Many packages will export to Word or HTML, so maybe you can keep a copy in one of those...

The only way to do this that I think of right now is with Dynamic SQL, which I don't recommend.

I'd just build in the time it takes to make the...

You must be adding data to the mdf, as mentioned above. That's why it grows. To stop it from growing, stop adding data.

You should have an idea of growth and...

I'd use Sergiy's method, but if you don't want nulls, use

if @x is not null

instead. It's cleaner.

Are you connecting with TCP/IP? It's possible that SQL was installed without TCPIP. You can check the beginning of the SQL Server error log to see which IPs it's listening...

The proxy needs to know to forward port 1500 to the outside IP. I believe by default this is not the case with most proxy servers.

Be sure their firewall also...