.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
Sharon Maxwell
Post New Web Links

Proper upgrade path for out of date SQL instance

Posted By:      Posted Date: August 31, 2010    Points: 0   Category :Sql Server
 
I currently have a SQL backend that is feeding an out of date MOSS 2007 instance.  I have found the following: Version Information   Version 9.00.4053.00 Command: Select @@Version Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)   May 26 2009 14:24:20   Copyright (c) 1988-2005 Microsoft Corporation  Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2) Version Number KB Article Link Release Date 9.00.4305 SQL Server 2005 SP3 CU10  June 2010 9.00.4294 SQL Server 2005 SP3 CU9 Apr 2010 9.00.4285 SQL Server 2005 SP3 CU8 Feb 2010 9.00.4273 SQL Server 2005 SP3 CU7 Dec 2009 9.00.4266 SQL Server 2005 SP3 CU6 Oct 2009 9.00.4230 SQL Server 2005 SP3 CU5 Aug 2009 9.00.4226 SQL Server 2005 SP3 CU4 June 2009 9.00.4220 SQL Server 2005 SP3 CU3 Apr 2009 9.00.4211 SQL Server 2005 SP3 CU2 Feb 2009 9.00.4207 SQL Server 2005 SP3 CU1 Dec 2008 9.00.4053 SQL Server 2005 SP3 GDR (Security Update) Oct 2009 9.00.4035 SQL Server 2005 SP3 Dec 2008 9.00.3356 SQL Server 2005 SP2 CU17 Dec 2009 Whats the best approach to updating the SQL instance?  Do them in order or can I use the latest cumulative?  Any other issues I should be concerned about?


View Complete Post


More Related Resource Links

Proper upgrade path for out of date portal

  
I have a MOSS 2007 Portal that is woefully neglected.  A quick glance showed that its version was 12.0.0.6219.  The table below list all the current updates. 12.0.0.6520 Cumulative Update KB974989 & KB974988 Oct 2009 12.0.0.6514 Cumulative Update KB973410 & KB973409 Oct 2009 12.0.0.6510 Cumulative Update KB971538 & KB972569 Jul 2009 12.0.0.6504 Cumulative Update KB968857, KB968850, &KB968851 Jun 2009 12.0.0.6421 SP2 April 2009 12.0.0.6341 Cumulative Update KB963654 & KB961755 Feb 2009 12.0.0.6335 Cumulative Update KB960010 & KB960011 Dec 2008 12.0.0.6327 Cumulative Update KB956056 & KB956057 Aug 2008 12.0.0.6318 Infrastructure Update KB951695 & KB951297 Jul 2008 12.0.0.6303 SP1 + KB948945 Feb 2008 12.0.0.6301 SP1 + KB941274 Jan 2008 12.0.0.6300 SP1 + KB941422 Jan 2008 12.0.0.6219 SP1   12.0.0.6039 October 2007 public update   Do I have to apply them all in order or can I simply jump straight to the cumulatives in order?  Are there any of other considerations I should be aware of?

Feature Upgrade Functionality - Adding a new Content Type and List Instance

  
I've successfully used the upgrade functionality in SP 2010 to upgrade my list structures as needed. So far, these updates have been adding new fields to existing content types. Now, I have some new fields, content types and list instances to add, and am having trouble getting this accomplished. The scenario is this: - A new content type with a single custom field (also new), and a list instance for this new content type - A new field that is a lookup back to the new list instance defined above. This new field is added as an existing content type. - In my feature.xml, I have the Element Manifest specified with both new fields and an AddContentTypeField element for the new field being added to an existing content type:   <ApplyElementManifests> <ElementManifest Location="V1_04\Elements.xml"/> </ApplyElementManifests> <AddContentTypeField ContentTypeId="0x0100..." FieldId="{8028A1C8-1147-4DF7-B5C3-8A1F84A30360}" PushDown="TRUE"/> The result of running the update on this feature is: - My new field that is part of an existing content type is added - My new field that is part of a new content type/instance is added - My new content type and list instance is NOT created, therefore my lookup is broken Any idea why my new Content Type and List Instance is not being created? Do I need to specify there

Feature Upgrade Functionality - Adding a new Content Type and List Instance

  
I've successfully used the upgrade functionality in SP 2010 to upgrade my list structures as needed. So far, these updates have been adding new fields to existing content types. Now, I have some new fields, content types and list instances to add, and am having trouble getting this accomplished. The scenario is this: - A new content type with a single custom field (also new), and a list instance for this new content type - A new field that is a lookup back to the new list instance defined above. This new field is added as an existing content type. - In my feature.xml, I have the Element Manifest specified with both new fields and an AddContentTypeField element for the new field being added to an existing content type:   <ApplyElementManifests> <ElementManifest Location="V1_04\Elements.xml"/> </ApplyElementManifests> <AddContentTypeField ContentTypeId="0x0100..." FieldId="{8028A1C8-1147-4DF7-B5C3-8A1F84A30360}" PushDown="TRUE"/> The result of running the update on this feature is: - My new field that is part of an existing content type is added - My new field that is part of a new content type/instance is added - My new content type and list instance is NOT created, therefore my lookup is broken Any idea why my new Content Type and List Instance is not being created? Do I need to specify there

sql server 2008 version upgrade failed access to path is denied

  
upgrading from 2008 r2 eval to 2008 r2 enterprise. Use the maintenance option from setup. Get pretty far along in the process.  But then the following error. ( an additional note. setup warns that I am running sql server on a domain controller server. ) The link the error message points to has nothing to say. Why would my sql server upgrade fail? If I have to reinstall, will I lose my database data? thanks,   TITLE: Microsoft SQL Server 2008 R2 Setup ------------------------------ The following error has occurred: Access to the path 'C:\Program Files\Microsoft SQL Server\100\License Terms\SQLServer2008R2_License_ENT_1033.rtf' is denied. Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0x60797DC7%25400xBB814387  

service pack 3 upgrade deployment on a specific instance possible and wise?

  

Hi All,

I'm running a SQL Server 2005 SP2 test server with two instances, both with service pack 2.

If I would like to test service pack 3, would it be possible or wise to upgrade one of the instances to service pack 3 for testing purposes (i will restore production data on top of it)?

Best regards


Business Intelligence professional

XMLdocument check if path exists (selectnodes throws "Object reference not set to an instance of an

  

Normally the code below works, EXCEPT if the xpath doesnt exist, then I get the error "Object reference not set to an instance of an object." on the 2nd line


Dim sessionXML As XmlDocument = Session("XML")
If sessionXML.SelectNodes("//root/data/compare/locations/location") IsNot Nothing Then

How can I check if the xpath exists (without a try catch preferably)?


SQL 2008 SP2 succefull but instance start fails - Script level upgrade for database 'master' faile

  

after installing SP2 instance starts and stops with error:

Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 5831, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.

Already tried without success:
- enabled SA account (was disabled) http://support.microsoft.com/kb/960781/en-us
- uninstalled SP2 -> other error, but same problems with running the script

 

 


Date Covertion from Char field to a proper format

  

Hi Gurus,

There is a field in a table with type and length as varchar(255).  It stores a value as follows 'Patch_Test_9_10_201012;00;00AM'.  I need to extract 9_10_201012;00;00AM and format it as 9/10/2010 12:00:00 AM.  I tried CONVERT and CONVERT+CAST it won't work.

Is there a way to do it? Please, any ideas , inputs are wellcome

SequelSequel


Best upgrade path 2005 exp to 2008 standard, different boxes

  

What would you recommend as the best way to convert our databases from SQL 2005 Express to SQL Standard which are both up and running on different servers?  I'd prefer to leave the old server as-is so we can transfer one or two databases per weekend and leave the others as-is.  Would a backup and restore work when switching version, as in method one in this article?: http://support.microsoft.com/kb/314546

Or would there be a better way, such as using an import?


date not getting stored in proper format in vb 6.0 and sql server 2000

  
i have a form which accept date in dd/mm/yyyy format from the user but  when i am storing it into sql server , some time it is getting stored in
dd/mm/yyyy format and some time in mm/dd/yyyy format. When i try to retrive date from sql server  and fetch it into text box it is geting  displayed in other format . some time in dd/mm/yyyy  and  mm/dd/yyyy format .
my reginal date setting is in mm/dd/yyyy format .
will be great if i get a quick help on this issue

SQL Server 2008 enterprise upgrade failed: Illegal characters in path.

  

My production upgrade from SQL Server 2005 to 2008 just went down. This is a single x64 server installation the log reported the strange set of problems:

 

2011-04-13 10:14:48 AS: Result: (Utility) Success
2011-04-13 10:14:48 AS: Action: Set Admin Rights For Folder(F:\SSAS\AS_TEMP\|)
2011-04-13 10:14:48 Slp: Sco: Attempting to set directory full path
2011-04-13 10:14:48 Slp: Sco: Attempting to normalize directory path F:\SSAS\AS_TEMP\|
2011-04-13 10:14:48 Slp: Prompting user if they want to retry this action due to the following failure:
2011-04-13 10:14:48 Slp: ----------------------------------------
2011-04-13 10:14:48 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2011-04-13 10:14:48 Slp: Inner exceptions are being indented
2011-04-13 10:14:48 Slp: 
2011-04-13 10:14:48 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
2011-04-13 10:14:48 Slp:   Message: 
2011-04-13 10:14:48 Slp:     Illegal characters in path.
2011-04-13 10:14:48 Slp:   Data: 
2011-04-13 10:14:48 Slp:    DisableRetry = true
2011-04-13 10:14:48 Slp:   Inner exc

Using a CompareValidator to check input is a valid date

  
The CompareValidator can do more than just compare two controls. You can also compare it against several of the main .net data types such as Date, Integer, Double and Currency.

To do this you would set Operator="DataTypeCheck" and instead of setting the ControlToCompare or ValueToCompare attributes as you normally would you use the Type="Date" (or any of the data types I have listed above).

How To Set a Date Format In GridView Using ASP.NET 2.0

  
A very common desire is to set a column of a gridview to display just the month, day and year of a DateTime type. The problem is the by default, the HtmlEncode property of the boundfield attribute (
The problem is that if this field is enabled, you can not pass format information to the boundfield control. That is, if you try the following code, you will not get the desired result.

jQuery Date picker Implementation in ASP.NET

  
I've posted a wrapper ASP.NET around the jQuery.UI Datepickercontrol. This small client side calendar control is compact, looks nice and is very easy to use and I've added it some time back to my control library.

This is primarily an update for the jQuery.ui version, and so I spend a few hours or so cleaning it up which wasn't as easy as it could have been since the API has changed quite drastically from Marc's original implementation. The biggest changes have to do with the theming integration and the resulting explosion of related resources.

If you want to use this component you can check it out a sample and the code here:

How to format datetime & date with century?

  
Execute the following Microsoft SQL Server T-SQL datetime, date and time formatting scripts in Management Studio Query Editor to demonstrate the usage of the multitude of temporal data formats available and the application of date / datetime functions.

http://www.sqlusa.com/bestpractices2005/centurydateformat/

Date and Time Functions in SQLSERVER

  
Date and time functions allow you to manipulate columns and variables with DATETIME and SMALLDATETIME data types.

1 DATEPART Function
2 DATENAME Function
3 DAY, MONTH, and YEAR Functions
4 GETDATE and GETUTCDATE Functions
5 DATEADD Functions
6 DATEDIFF Function
7 More SQL Server Functions

Data Types - Date and Time in SqlServer

  
Date and time values can be stored with either the DATETIME or SMALLDATETIME data type. The difference between the two is that SMALLDATETIME supports a smaller range of dates and does not give the same level of precision when accounting for time. The DATETIME data type can hold values from January 1st of 1753 to December 31st of 9999. The time is stored to the 1 three hundredths of a second and each value takes up 8 bytes of storage. The SMALLDATETIME data type can hold values between January 1st 1900 and June 6th of 2079. The time is tracked to the minute and each value takes up 4 bytes of storage. The majority of business applications can live happily with SMALLDATETIME, however, if you are in an environment where each second matters or you need to make estimates to the distant future (or past) then you have to resort to DATETIME. If you fail to specify the time when inserting a value into a DATETIME or SMALLDATETIME column, a default of midnight is used. If you fail to specify the date portion the default of January 1, 1900 is used.
Categories: 
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend