There are several views on this. I believe you can have the sa account disabled and still have it own jobs.

My recommendation is to either use sa or create...

Have a good time. Relax and...

If you get this working I'd be interested in seeing what you did.

I don't know enough about the database to know if your data would be in a consistent state if you restored to another database name and rebuilt the table from...

Thanks. It is working in SQL Scripts and the web site now.

Okay, I don't know how to do this within an SSDT project, but you might be able to create a PoSH script that iterates through script files in the post-deployment...

The best way to recover from this is to restore from a good backup.

It seems that the Search in the SQL Scripts SSMS add-in is also affected by this issue as no matter what I search for, nothing is returned there either, even...

I can confirm that search appears to be broken. I searched for SQL, T-SQL and Tally Table and got no results for any.

Sounds like a classic Gaps and Islands problem so you might want to look at this article[/url]

How do you know the package didn't do anything? If the you aren't dynamically creating the backup file names then the existing backup files with either be overwritten or...

<sarcasm>Advantage: you look like a hero when you make everything work better when you turn off the process that shrinks the database </sarcasm>

:w00t:

Yes it is possible. The easiest way is to create a group on clinic code and put a page break at the end of the group.

The benefit you get from using SSDT for database development is the database project itself not the environment. You get direct integration with TFS for source/version control, code...

Hmm, never seen that error before. A restore from backup would include resetting the identity value to what it was when the backup was taken, so that shouldn't cause...