Part of my test plans for development includes unit testing my stored procedures with known parameters and comparing the expected results with the actual results.

OK, in a production environment you...

Yes,

If you grant access via database roles then deny write access to the view for that particular role.

If you grant access to users (after a smack on the wrist) deny...

Kenneth, try using BETWEEN on a column with a clustered index and then comparing the > and < method.

If your SELECT involves a single table then you should be able to Add.

Make sure that whatever user you are connecting to the database has read/write access.

Your best bet is...

When it comes to WHERE clauses I have found that the different comparison operators have different performances.  In order of speed (fastest first)

1. =
2. > or <
3. <> or !=

If you can...

Theoretically you could simply run the Access upsizing wizard http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part2/c0561.mspx

I would start by reading up about the different datatypes in SQL Server and mapping them to the various MS...

When the proc is called from your application open up SQL Query Analyser and run sp_lock and sp_who to see what is going on.

Within Enterprise Manager have a look at...

If your users are administrator then you have big problems.

If you want to block Access and Excel usage then what rights should they legitimately hold?

What logon are they using?  Why...

If this procedure has been working fine with good performance then my first suspicion would be that something else is causing the problem.  Perhaps some long running process that is...

I've heard of modelling tools, but then I've heard of unicorns and phoenixes as well

To me Key = Index.

AK1 needs to be a unique key if you are going to do this, otherwise you will take an AK47 to your data integrity.

As...

Note POWER will give an arithmetic error if you exceed 31 issues because POWER can only return a 32 bit integer.

DECLARE @tbl TABLE(Id Int , Issue CHAR(8))

DECLARE @byLoop TinyInt

SET @byLoop=1

WHILE @byLoop<32

 BEGIN

  INSERT @tbl(Id , Issue)

  SELECT POWER(2,@byLoop-1),'Issue ' + CAST(@byLoop AS VARCHAR(2))

  SET @byLoop=@byLoop+1

 END

SELECT * from @tbl

This design limits the number of possible values to:

• 31 if the Int field is used.
• 63 if the BigInt field is used.

If you are happy with that then why not prepopulate...

Personally I would have three tables.

• Customers
• Models
• CustomersToModels

If you haven't already done so I would create an integer field to act as the primary key for the Customers and Models table.

On the...