|
||||||
|
We are very excited to finally release our first “official” release of the admin database objects. While we are still not yet ready for the documentation (shocking, I know), the objects have gone through a fair amount of testing and we’re confident that your environment is ready to utilize them. Lots of new changes and some new objects since the last RC deployment. http://www.sqlslayer.com/wp/admin-database/ Enjoy! Similar to my Windows 2008 clustering adventures, I recently went through some problems when trying to cluster SQL 2008 on Windows 2008 R2. Long story short, you have to install SP1 prior to installing SQL or simply slipstream the install. The install blew up on: There was an error setting private property ‘RequireKerberos’ to value ‘1′ for resource ‘SQL Network Name (SERVERNAME)’. Error: Value does not fall within the expected range. To which I searched online to find that SP1 resolves the matter. So I went to uninstall, and then got this: The SQL Server failover cluster instance name ” could not be found as a cluster resource. Followed by this: There was an error attempting to remove the configuration of the product which prevents any other action from occuring. The current configuration of the product is being cancelled as a result. I tried to simply install SP1 to see what happens, and I get: A failure was detected for a previous installation, patch, or repair for instance ‘MYINSTANCE’ during configuration for features [SQL_Replication_Core_Inst,SQL_Engine_Core_Inst,MPT_AGENT_CORE_CNI,]. In order to apply this patch package (KB968369), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed. So basically at this point, I was stuck. I couldn’t install, uninstall nor repair. I ended up rebuilding the server, but after posting after at SQLServerCentral.com, I was given this link which I wish I would have tried: http://support.microsoft.com/kb/953505 Anyways, after I had the server rebuilt, I finally made myself a slipstream SP1 install, which ended up resolving the issue. I’ve also come to learn that you can simply install SP1 prior to the 2008 install and then install SP1 again after the engine install to resolve these matters. If you haven’t made yourself a slipstream install, I’d highly recommend it, and it’s incredibly easy: http://blogs.msdn.com/petersad/archive/2009/02/25/sql-server-2008-creating-a-merged-slisptream-drop.aspx Hope this helps. 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!
http://www.sqlslayer.com/wp/admin-database/
http://www.sqlslayer.com/wp/admin-database/
http://www.sqlslayer.com/wp/admin-database/
http://www.sqlslayer.com/wp/admin-database/
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: 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. 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. http://www.sqlslayer.com/wp/admin-database/
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 |
||||||
|
Copyright © 2010 SQL Slayer - All Rights Reserved |
||||||
Comments