Malcolm Daughtree (10/3/2007)

---

And my last comment is, that if you don't what people to use it then don't publish it on a free and open forum, someone will read it...

There are a variety of reasons for this error. Can you explain more about your setup (workstation / SQL Server on the same domain, Kerberos configured, etc.)?

Under what user context does the VB app run (context of the user or as a service account)? How does it connect to SQL Server (SQL Server login/Windows authentication)?

I prefer to use the technique described in this Microsoft KB article:

How to transfer logins and passwords between instances of SQL Server[/url]

It'll ensure your SIDs match up, meaning you won't...

Here is an idea...

Create views of the tables which do NOT reveal the columns. Grant access to the views. Revoke access to the tables for those users. It's the quickest...

Blog readers are a separate animal entirely. In a lot of cases I'll be reading something in my blog reader and if I find it interesting that I want to...

Strommy (10/3/2007)

---

I must say I am jealous. Mr. Kelly's solution is far easier and elegant. The only down-side is having to teach Enterprise Manager addicts how to use...

In SQL Server 2000, there is no...

The recommendation is to do so at the schema level. The reason for...

One thing to remember is that with pooling in effect, if you close a connection, the operating system is going to hold it open for a length of time (the...

I don't believe SQL Server 2000 has a way to tell this. However if your local security policy is set up right (whether configured on the server or through a...

You know, it might. The monitoring agents do for products like HP's set. I know SQL Server has a MIB that can be imported, but it's not actually something I've...

Sure. Sit down with the folks who will actually use the system. Ask them, "From here, where would you typically go next?" and build the links accordingly. Sometimes giving them...

If you are specifying a default instance, than the port 1433 doesn't need to be specified. The client should try to connect to that port by default. If the port...

Not exactly. IIS is designed to take credentials, such as through basic auth and validate that to a Windows user account. SQL Server is not. You see issues like this...