Ever figure it out?

Some random things to check:

1. Is the Excel file set to read-only on the production server?

2. Does the SQL Server service account have permission to read the...

GilaMonster (3/13/2012)

---

32 bit with /3GB and...

Whisper9999 (2/27/2012)

---

We've got 2005 Enterprise Edition (SP3) on a cluster. This is actually a dev cluster, so we need to switch it to the dev edition of SQL Server.

So...

2.54 is a number I recognize. Are you by any chance on a 32-bit OS with the /3GB switch enabled but without AWE enabled?

Do you have a SQL 2008 instance anywhere in your environment? Even a shared dev or private local instance? If so, or if you can stand one up, you can...

Anytime, happy to assist 😀

Carol Adams (3/6/2012)

---

I have been assigned the responsibility to find a product to use for source/version control with our SQL databases.

I have seen Red-Gate Source Control, but need to show...

You should be fine updating the subscriber (reporting instance) and leaving the publisher (live) alone. You are running a newer build on the reporting instance already so that makes it...

What an excellent article. Thank you for sharing!

The configuration I recently implemented (AWE=Yes,3GB=Yes) apparently enables SQL Server to access all 4GB of the physical memory. At the same time...

balasach82 (3/10/2012)

---

I am using BCP out to extract some 50 records into excel. In table, the records are sorted correctly (ie by datetime on which record is inserted). But when...

PHXHoward (3/13/2012)

---

Thanks for all the great information.

The Microsoft rep that we have on site this week confirmed that enabling AWE and LPIM on the 4gb RAM 32bit system would allow...

I automate this kind of admin work all the time. It's code generating code, but it's not a cursor and performs quite well up the point where db admin tasks...

If you use SQL Agent, there is no need to introduce an additional programming domain into the call stack. Ditch xp_CmdShell and call bcp from a step with type CmdExec.

SSIS...

You could try some slight-of-hand. Restore the DB, then change your DB-context to the new DB and immediately set it to SINGLE_USER mode. This will lock everyone else out except...

No. For msdb, model and tempdb issue ALTER DATABASE...MODIFY FILE to set them to the new location, shut down the instance, move the files (except tempdb, just delete files), then...