Recent content by SQLSquirrel

Hello, My clients have called because they cannot access BRIO 6.6 due to the above message being displayed when they try to login. The main users are on holiday (as are the other support staff) so one of the junior staff has phoned me (clutching at straws!). Unfortunately I'm no expert on BRIO...

Thanks for that, I suspected it would come to this!

In SQLServer 2005, I am building some T-SQL scripts to semi automate a data masking process (as per a ridiculous requirement from my client*). During one pass of the database I need to exclude any columns which are referenced by a trigger but I am rather perplexed (so far) as to how to...

Sadly the IP address didn't work, and niether did "Netsh int ip set chimney DISABLED" as mentioned as a workaround in the MS article (although my error message didn't quite match the ones in the text I was optomistic that this would be a fix - damn!).

Yes it does crash every time. I'll try using the IP address instead - it's not a method I like because IP's can change more often than a server name - but then again I'll try anything under the circumstances. Thanks

Limiting the process to one rocessor made no difference.

My users have a VB6 application which calculates premium payments (to be requested via letter) for approximately 1000 life insurance policies. This app was recompiled for XP/SQL 2005 and runs okay without any modification on our test XP pc (single processor) against our test SQLServer 2005...

Oh no! I have just run a DBCC CHECKALLOC (dbname) and encountered the following messages on one of our largest SQLServer 7.0 databases. Server: Msg 8968, Level 16, State 10, Line 1 Table Corrupt: IAM page (1:892478) (object ID 2, index ID 255) is out of the range of this database. DBCC results...

Forgot to mention it's on SQLServer 7.0

Oh no! I have just run a DBCC CHECKALLOC (dbname) and encountered the following messages on one of our largest databases... Server: Msg 8968, Level 16, State 10, Line 1 Table Corrupt: IAM page (1:892478) (object ID 2, index ID 255) is out of the range of this database. DBCC results for...

Can someone suggest and/or supply a quick and efficient generic solution to identifying the most recent access (date/time/logon id) on a SQLServer (7.0 and/or 2000) database? (excluding the id used by the SQLAgent)?

I have an NT4 workstation running VB code which has the functionality to change, and does successfully change, the orientation of the output if printing to an HP Laserjet or Xerox printer. If the printer is switched to an IBM Infoprint 1352, the functionality within the VB code to change the...

We have several data extracts on a single MI database which is fed by replication from 5 other databases - on 5 other servers. I recently paused replication (manually on all 5 servers) and this seemed to improve the MI extracts performance (run by SQL:Agent tasks). Now I'd like to pause/restart...

Stunning! You prompted me to remember that the housekeeping tasks for two of these three databases (the ones which fail) include steps to switch compatability levels back and forth between 6.5 and 7.0 (a feature required by our third party application to support code inherited from a previous...

Both servers are SQL 7.00.1094 (sp4) cheers