149 reputation
9
bio website cyberimpact.com
location Mascouche, Canada
age 35
visits member for 5 years, 1 month
seen yesterday

Currently principal developer of Cyberimpact (white hat mass mailing web app) at Cyber Generation. Expertise in

  • PHP
  • CodeIgniter
  • SQL Server, T-SQL
  • PostgreSQL
  • Regex
  • javascript, AJAX, jQuery, prototype.js
  • Classic ASP, VbScript (no comments...)

Jan
18
comment SQL Server 2008 intermitent error 40 running parallel queries
I updated my question to include the new error when using TCP/IP only connection.
Jan
15
comment SQL Server 2008 intermitent error 40 running parallel queries
How do you do that ?
May
26
comment Sql Server differential backup : Simple vs Full recovery model
Thank you, your short answer and link helped much!
Feb
25
comment How to revert the compressed attribute on files in Windows for a whole drive
Works great thank you :-) I just needed to alter a bit your suggested query to : compact /u /s /i d:* /i ignores errors (I got one a certain point for system volume folder) d:* (I added * to include all files)
Feb
25
comment How to revert the compressed attribute on files in Windows for a whole drive
That was done by mistake by a sysadmin that does not work here anymore ;-) Other sysadmins did not know how to revert this, that's why I'm asking here.
Jan
7
comment SQL Server 2008 log file grow ultra huge even in simple recovery
As we did not know the first time it occured that the logfile would get that big, and did not know also that shrinking from 37GB to 1MB was a matter of a few seconds, we waited until the next day before running the Shrink command, and the next day the logfile was still 37GB. Autoshrink is not turned on for that DB, which I think explains why it remained 37GB. My question turns out more like how can we avoind to get it up to 37GB, we though that simple recovery would prevent that.
Jan
6
comment SQL Server 2008 log file grow ultra huge even in simple recovery
That would be something worth to try, but it does not explain why the log file keeps its huge size after the Stored Procedure finishes, why don't it shrinks back automatically to 1MB.