In response to Alvin's post, it has been brought to attention for a long time ago but because of application vendor support issues it was planned to be migrated next...

Lowell (11/11/2015)

---

could you be misinterpreting object_id as an identity column in sys.objects?

sysobjects get an id based on an increment of some weird number which i didn't remember but could find...

Luis Cazares (11/11/2015)

---

I'm not sure there's something documenting either that the id is reusable nor it's completely unique. It might not be an identity either if that's what you were...

For Microsoft OLEDB Provider for DB2, it requires enterprise or developer edition.

For IBM client access, yes, standard ed is just fine.

Since you have AS400 systems, I'm assuming you're entitled for ibm support, so you may wanna go for ClientAccess and have it installed on your standard ed sql. If you...

What edition of sql server do you have in your production server? Verify if you have the enterprise edition.

You may download DB2OLEDB packages here (not sure if these are the...

MS ole db provider for db2 requires Enterprise edition of sql.

..and I believe for you to obtain IBM IseriesClientAccess software from IBM site, you'll need IBM userid/password if you are...

You may want to script out your publication in case you would need to recreate it again. I would drop the publication and disable (sp_replicationdboption) publishing of the db. Then...

What does the log_reuse_wait gives you if you query sys.databases?

We have a few of our queries that we had the option MAXDOP set to 8 in one of our servers (16 CPUs). These queries used to throw out scheduler...

I came across this scenario in one of my tests where I tried using a usb drive for the tempdb, and yes it did start sql, and just recreated new...

I'm not sure if you can achieve it on a server or db level setting, I'd be interested to know as well,. but one thing you can do to help...

This has been a common problem, I read somewhere and they said it has something to do with the Jet driver? Anyway, I tried adding a macro in my template...

Your db's syspublications and syssubscriptions were lost, or had the prod's copy when you restored it with keep_replication and your distribution db still has the dev's publication/subscription info.

Do you have...

How about increasing the frequency of your tlog backups? And make sure your logreader is working, otherwise your log space won't be cleared if logreader isn't running even after you...