Actually, more so on...

Your client PC's are running an x86 OS - and therefore require an x86 driver to connect to a database. The client PC does not care, nor even know...

Without access to backups (that...

Without a backup - your only other option is going to be a log reader tool. That will only work if your database is in full recovery model and...

derreckdean (7/10/2009)It's a brand-new SQL Server 2008 install on a freshly-wiped box. I'm logged in as Administrator using NTLM auth.

I tried to reattach the DB as SA, no dice....

You can query WMI to get the processor counts, however - you might need to apply a patch first:

http://support.microsoft.com/kb/932370/

Could it possibly be a permissions issue? Are you logging into SQL Server with a privileged account or a user account?

Try running sp_change_users_login with the report option and see...

sanderstad (7/10/2009)

---

I know the consequenses about setting the recovery mode etc and I don't want to set it to simple because I want to be able to restore to a...

I could see a different execution plan being generated - but not different results. Both queries should return the same results and the fact that they are different says...

I have to agree with Jack - you are pretty much screwed. My guess is that you copied the mdf/ldf files for that database from a particular directory, and...

I didn't even think about that issue, although I have run into it a couple of times. Normally, it shows up in the history for the maintenance plan on...

Here is a different method (thanks Lynn for the setup):

If object_id('tempdb..#temp', 'U') Is Not Null

Drop Table #temp;

Create Table #temp (time char(4));

Insert Into #temp

Select '0900'

...

Right-click on SQL Server Agent, go to properties and select the Alert page and verify that this is configured for Database Mail.

Not sure this will fix your problem.

Did you validate that the SQL Server Agent Alert system has been setup?

Glad I could help