Sure, find the job/maint plan that runs it and disable that job. CheckDB does not run automatically. There is a job or maintenance plan that runs it.
However, that is really bad practice and not a solution. You need to be running checkDB somehow so that you can detect corruption before it affects the users, before it becomes irreparable. For some ideas for checkDB on very large databases see - http://sqlskills.com/BLOGS/PAUL/post/CHECKDB-From-Every-Angle-Consistency-Checking-Options-for-a-VLDB.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability