If you are talking about forms authentication from an asp.net web page it basically means "You do your own security"

So you'd need a database table with the usernames and passwords...

I'd start with the criteria "How many ways can it be adjusted". If it can be properly adjusted for lumbar support, height, tilt, arms etc, etc, then you have a...

We've got several virtual servers spread over various physical servers and one use is to replace old sql servers which are being gradually phased out e.g. the SQL2000 test server...

I'm another voracious reader - mostly non-fiction but eagerly awaiting the new Terry Pratchett novel.

I don't do e-books but I was brought up to use and appreciate the free public...

If this was one of your production sql databases then you would be restoring it from the backup onto...

I use the same lines as Manie - I don't do hardware but it's also somewhat of an advantage being a middle aged woman as people don't believe you really...

No one in the UK would want to go back down to only 4 weeks paid holiday. That was the norm thirty years ago when I started in IT. 5...

We use one sql account for each application as all are web based. That account is then ideally given only execute permission on stored procedures and functions.

On older badly...

If you are uncertain of your network connection and want to ensure the backup doesn't fail because of it, use a sql agent job where step 1 backs up to...

I'd recommend re-designing in SSIS anytime! There's so much better functionality that we've combined multiple dts into one ssis in many cases and found much better ways of doing jobs...

Run the performance dashboard reports and have a look at long running queries and missing indexes.

Is your machine at the same patch and service pack level as the server?

Was it saved as encrypt with user key by a different user or login?

Instances can also be useful if you have one server but need to pretend it's more! We have our development instance and our test instance co-existing happily on one server...

Our preference is to store a copy of the package in msdb because we can "Rely on server security" and save the connection details and passwords, especially good when importing...

I always use "Save copy of package as" from BIDS/Visual Studio and save to the SQL Server (msdb) and set the protection to "Rely on server..." and this saves all...