Forum Posts

Visitors Online

Admin database 1.5 RC1 is available

http://www.sqlslayer.com/wp/admin-database/

We’re one step closer to having our first “official” release with this latest release. The configuration now properly supports build specific as well as 2008. Next step is to make an update to the utility and finish up the documentation. We’re almost there!

  • Rewrote configuration to use new buildMin and buildMax parameters.
  • Fixed collation problem with CheckDB/FileIO and MoveDatabase (2000 versions).
  • Added TRACE permissions for PwrUser and Captain for StandardGroupPermissions.

Admin database 1.4 RC1 is available

http://www.sqlslayer.com/wp/admin-database/

  • Added a new view to show last time a user logged in and what database they accessed. Credit given to Jack Corbett.

Admin database 1.3 RC3 is available

http://www.sqlslayer.com/wp/admin-database/

  • who/who_vw: Added net_transport and auth_scheme
  • JobOperators: Added checks to make sure @Email, @Page or @NetSend was passed, Fixed Changed column to properly display that a job was updated

Admin database 1.3 RC2 is available

http://www.sqlslayer.com/wp/admin-database/

  • Added LRTRIM/RTRIM to several of the who columns (who procs and view).
  • Added exclusion for QueueReader job steps in JobLogging.

Admin database 1.3 RC1 is available

http://www.sqlslayer.com/wp/admin-database/

  • Resolved issue with SQLServerStartupNotification blowing up when additional startup procedures existed.
  • Enhanced maintenance procedures for more selective maintenance.
  • Added JobOperators procedure.

Scripting out agent jobs that call DTS packages in SSMS 2008

Experienced a rather odd problem today … I scripted out multiple jobs from a SQL2000 environment using SSMS 2008 that call DTS packages. The command line for the jobs looked like DTSRUN /S “Server\Instance” /N “PackageName” /E. When I ran the jobs, they continually returned:
DTSRun: Loading…
Error: -2147467259 (80004005); Provider Error: 17 (11)
Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0

I then took the command to a command prompt locally on the server, and the same error presented itself. Without going into all the other troubleshooting I did to find resolution, the problem ended up being that when using SSMS 2008, somehow there were hidden ascii characters in the command line. I found resolution by simply retyping the command. I then verified that the problem was indeed SSMS 2008 as I used SSMS 2005 to script and recreate the job again, and it worked without problem.

Hope others find this helpful.

“RowGUID is neither a DataColumn nor a DataRelation for table summary. (System.Data)”

We had merge replication in SQL Server 2005 set up that was working fine, except when trying to view conflicts, the Conflict Viewer would give this error: “RowGUID is neither a DataColumn nor a DataRelation for table summary. (System.Data)”.

The source of this it turns out was actually a period in the Publication name, as we had a “6.1” as part of the name. Other special characters would probably also cause trouble.

The only way to fix this was to drop the replication, resolve known conflicts manually with a data compare, recreate the replication, and reinitialize. After that, we could use the Conflict Viewer to resolve conflicts successfully.

This was a frustrating issue since the replication was allowed to be created with the period and worked completely fine, only the Conflict Viewer experienced trouble and it gave an error that did not accurately describe the issue.

The moral of the story is: don’t create a publication with a period in the name.

Admin database 1.2 RC3 is available

http://www.sqlslayer.com/wp/admin-database/

  • Removed model database from BackupDB

We are finalizing a new version of the admin update utility which will better support specific versions of SQL (ie two part OBJECT_ID was not supported until 2005 SP2), as well as better support 2008. Once we have updated the configuration, we are planning to release an official release of the objects. There is also hope that we will have official documentation ready as well. Please bear with us!

Thanks

Admin database 1.2 RC2 is available

http://www.sqlslayer.com/wp/admin-database/

  • Minor bug fixes for ChangeOwner, JobLogging
  • File naming enhancements for Trace_Blocking

Admin database 1.2 RC1 is available

http://www.sqlslayer.com/wp/admin-database/

  • Added support for RedGate backups
  • Added additional permissions for StandardGroupPermissions and new roles
  • Removed two part object_name call in CHECKDB for support pre-SP2
  • Resolved problem where ‘renamed’ column was not being updated when database owner was changed with ChangeOwner
Page 1 of 3123