Why am I developing an aversion to bit fields?

They seem to be responsible for unexpected wierdness - see for example thread "Why does this scan an entire NC index?"...

According to Books Online "The ROWGUIDCOL property is primarily used by SQL Server replication."

The same page (Using uniqueidentifier Data) goes on to give some reasons not to use UniqueIdentifiers.

Dumb question:

What happens if you change the two bit fields to [tiny]int?

I think I'm working up an aversion to bit fields.

Regards

Otto

Just tried your original code on my machine. Works fine connecting to the default server and the named instance.

Just a thought: you won't see the output unless you open the...

Did you really use 'Initial Caltlog' (sic) in your code or was that an typo when posting? Same for 'Ingetrated Security' (sic).

I tried the following code on my machine:

Option Explicit

Sub...

I had the same problem in an application I wrote. At the time I was working for a U.S. company (guess what server settings they used) but with salesmen throughout Europe...

Another thought: You shouldn't be using the sa account for normal use of SQL/Server. Ideally, only use windows authentication and not mixed mode. - but that's probably a subject for another...

Is the machine your computer or a remote server?

If it's your local machine try "Data Source=(local);"

You wrote that the default instance uses windows authentication. If this is the case,...

Standard answer: it depends.

In theory the answer is Yes. SQL/Server can handle several databases on the same instance.

In practice, it depends on the load each application generates. If they are only generating a...

I did a bit more digging on the 'restricted set of values' theme

I tried the following variants of the StatusUpdated column:

bit

Integer

Integer with a check constraint (StatusUpdated in (0, 1))

Char(1)

Char(1) with...

Perhaps another piece of the puzzle:

When I was testing, i tried to do a DBCC Show_Statistics on the index. With StatusUpdated defined as in int, it returned the three grids...

I think the culprit is the Bit specification on StatusUpdated.

I changed it to int, and the query plan uses the IX_StatusUpdated.

My guess is that the query optimiser looks at the...

Sorry to dissapoint.

I think the scripting engine simply processes objects alphabetically. So if object 'a' depends on object 'z' and you want to reload using the generated script... tough luck!...

Updating the statistics should have helped. If you run the select in query Analyzer with the Execution plan turned on it should now use a table scan and take around...

Did you run the select statement in Query Analyzer with the 'Show Execution Plan' option turned on?

I suspect your query is doing an index scan then a bookmark lookup.

With...