Viewing 15 posts - 37,411 through 37,425 (of 39,511 total)
You would need to build your own algorithm to encrypt/decrypt. I would store the key in a table (lock this down) and use a UDF to perform the encryption.
Steve Jones
June 19, 2002 at 4:45 pm
Is it a large result set? If so, the rendering may be longer in ASP. Also, did you run your VB app from the web server?
Steve Jones
June 19, 2002 at 3:05 pm
I would use the ExecuteSQL task, but if you use Active X, you would essentially use an ADODB Command object and a RECORDSet object and submit the SQL needed. You...
June 19, 2002 at 3:03 pm
Is this 2000 or 7? Any other issues? Also, what version of client tools to you have?
Steve Jones
June 19, 2002 at 11:51 am
You can do this, but the information has potentially been comprimised by transitting the wire unencrypted.
You would set the trigger to update the column with the envrypted value using some...
June 19, 2002 at 11:50 am
Agree with Antares. The server load will vary and it is possible this report is right near the timeout window. No load may run ( or if data cached) and...
June 18, 2002 at 4:41 pm
Extents are fixed sizes. The data gets fragmented when the extents used for a table are not physically near each other. Rebuilding the clsutered index will reorganize these.
Steve Jones
June 18, 2002 at 2:50 pm
Extents are fixed sizes. The data gets fragmented when the extents used for a table are not physically near each other. Rebuilding the clsutered index will reorganize these.
Steve Jones
June 18, 2002 at 2:50 pm
June 18, 2002 at 2:49 pm
Agree with above. Best to try and "rethink" the problem as a positive rather than a negative.
Steve Jones
June 18, 2002 at 1:26 pm
If you use SQL-DMO, there is a method to look for SQL installations. Note that this may not work, especially if you are subnetted.
Check the MSDN docs
Steve Jones
June 17, 2002 at 1:40 pm
It is a straightforward change. I don't think there are any new keywords. If there are, you can always set the databases to run as sql 7 compatible.
Steve Jones
June 17, 2002 at 1:35 pm
Check in the control panel for the MSSQL service account. Likely it was an account in the old domain. Set it to a new account in this domain.
Steve Jones
June 17, 2002 at 1:33 pm
Not a SQL error. you have an error with the IIS account loading the DLL. Track that down first. The "knowing where the server is" is stricly a location item....
June 14, 2002 at 3:27 pm
Can you double check the PK on the table? Also , try importing a small batch with duplicate and non-duplicates to verify it works.
Steve Jones
June 14, 2002 at 3:23 pm
Viewing 15 posts - 37,411 through 37,425 (of 39,511 total)