So it's just that it will cause SQL Server to not use all the physical memory, not that it will cause the Zombiepacolypse or something equally horrendous, right?

Silly question that may not have anything to do with anything... Are you sure that the drive / folder in question has enough disk space for that database to even...

Then consider your issue might be that you have too much database and not enough memory. Altering the memory allocation is unlikely to fix performance issues if the server is...

sqlfriends (6/9/2011)

---

It's impossible for us now to get another sandbox for us to play with, no budget for that, the server hosts 4 vendor applciations related with network monitoring, ITSM,...

jcrawf02 (6/9/2011)

---

Jim Murphy (6/9/2011)

---

Congrats Gail! That's awesome.

The best part is that your posts are not useless point-getting restatements. Grrrr, I hate those. You post...

Have you ever gone to that network location and verified that the file is still there?

Have you ever run a network sniffer to make sure you weren't disconnected at the...

We have scripted backups that run as SQL Jobs via Litespeed and we never see those messages.

Does the ADO need to run the script itself or can it just...

Again, it depends, but I believe the blanket recommendation is to let SQL Server figure out memory allocation for itself unless you are having problems.

Too many people don't understand what...

Kevin,

as I have not run into this situation, I am genuinely curious. What's the downside of running both at the...

Apparently not if they haven't posted a reply.

Two suggestions for you.

1) Google the error message.

2) Make sure you can connect to your data source outside of the report using...

We definitely need to see not only more code (because what you posted doesn't give us enough information), but we need to see table structure and sample data (if the...

I hope it will too.

Let us know if you have any other questions.

You can use the MSDB fixed database roles to grant your users the ability to run jobs. The SQLAgentUserRole can be granted to the users, then have the specific job...

I wouldn't bet on it. There's no way of telling what functions, procs, or object changes (datatypes, system tables) happened between SPs to fix whatever problems Microsoft may have found...

My immediate recommendation is to get the other applications off your SQL Server. Otherwise they will cause even more problems in the future.

As far as setting SQL to a specific...