To all intents & purposes... Jinx!

If you're going with ad hoc queries, save yourself the headaches and just write the code directly against each database. The performance won't be any worse and the development and...

I'm not entirely sure I understand the question, but I'll take a shot.

You can export the entire schema to a single SQL file. Then you can use a third party...

Yeah, I've seen SINGLE_USER fail too. There is a lag, however tiny, between that GO statement and the next statement in the batch. It only takes one connection to muck...

mailsar (6/2/2008)

---

Hi all,

I am in the process of creating few tables and indexes. I am creating a vendor table and a service table. The Vendor and service...

This works, but be careful, it will cause data loss to open transactions.

ALTER DATABASE [dbname]

SET SINGLE_USER --or RESTRICTED_USER

WITH ROLLBACK IMMEDIATE;

GO

DROP DATABASE [dbname];

GO

What about a constraint or a rule? Something seems to be affecting the PK or reaching out to these other tables. I just did a couple of tests. I can...

In addition to the trigger, are any of the columns affected by the update statement (or by the trigger) part of the primary key of the table? If so, you're...

Are you running more than just SQL Server on the box? That will likely lead to problems later. SQL Server tends to use quite a lot of memory and processor....

I'd work on making adjustments to the code or the application server so that it doesn't make these types of calls. They shouldn't be required and there's probably a way...

As Jeff and the others have already said, no, you don't need to put these abbreviations, or any others, in front of the views and stored procedures. However, I'll give...

SQL Prompt does take some practice to get used to it being involved with your TSQL. I've gotten rather good at hitting the 'Esc' key when I know it's just...

Really, never?

I find the percentage of the batch to be a pretty useful guide most of the time. Not all of the time, no, but more often than not.

Transactions on databases are generally short. Actually they should be as short as possible most of the time. That means a small entry in the log. That log gets truncated...

Not as such, no. I was just trying to get an understanding of how things were configured. If you're truncating on checkpoint, uh, I mean, in simple recovery mode, then...