Showing posts with label upgrading. Show all posts
Showing posts with label upgrading. Show all posts

Thursday, March 22, 2012

32 bit vs. 64 bit

I'm running SQL Workgroup edition (32 bit) on a 64 bit OS. Would I see a performance gain from upgrading to SQL Standard 64 bit? Hardware is DL385 2 proc AMD 2.8 Ghz with 6 GB RAM. Has anyone made this comparison and how much gain did you see?

I am not sure the performance that can be obtained. But one thing is clear that upgrading 32-bit to 64-bit is not supported directly. If you really want to perform such an upgrading, you can do as follows.

Approach one.

1. Uninstall 32-bit and save database

2. Install 64-bit and attach the saved database

Approach two.

1. Install 64-bit side by side with 32-bit, which is supported.

2. Export 32-bit data to 64-bit.

3. Uninstall 32-bit.

Anyway, please backup your database before doing any major operation on your database.

32 bit vs. 64 bit

I'm running SQL Workgroup edition (32 bit) on a 64 bit OS. Would I see a performance gain from upgrading to SQL Standard 64 bit? Hardware is DL385 2 proc AMD 2.8 Ghz with 6 GB RAM. Has anyone made this comparison and how much gain did you see?

I am not sure the performance that can be obtained. But one thing is clear that upgrading 32-bit to 64-bit is not supported directly. If you really want to perform such an upgrading, you can do as follows.

Approach one.

1. Uninstall 32-bit and save database

2. Install 64-bit and attach the saved database

Approach two.

1. Install 64-bit side by side with 32-bit, which is supported.

2. Export 32-bit data to 64-bit.

3. Uninstall 32-bit.

Anyway, please backup your database before doing any major operation on your database.

Saturday, February 25, 2012

2005 SP2: failed to modify maintenance paln

After upgrading to SP2, I created a maintenance plan in the management studio using the wizard. The plan executes OK. But when I tried to modify it, I got the following error, and cannot load and modify:

Value cannot be null.
Parameter name: component (System.Design)

Please help ASAP.

Ed

Can you please submit this as a defect on Microsoft Connect? Please include steps to reproduce the problem, screen shots, and as much details information about the error message (sometimes you can copy the "stack trace" which is very useful to our dev team).

Microsoft Connect:
http://connect.microsoft.com/SQLServer/Feedback/

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1266171&SiteID=1 fyi on this aspect.

2005 SP2: failed to modify maintenance paln

After upgrading to SP2, I created a maintenance plan in the management studio using the wizard. The plan executes OK. But when I tried to modify it, I got the following error, and cannot load and modify:

Value cannot be null.
Parameter name: component (System.Design)

Please help ASAP.

Ed

Can you please submit this as a defect on Microsoft Connect? Please include steps to reproduce the problem, screen shots, and as much details information about the error message (sometimes you can copy the "stack trace" which is very useful to our dev team).

Microsoft Connect:
http://connect.microsoft.com/SQLServer/Feedback/

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1266171&SiteID=1 fyi on this aspect.

Saturday, February 11, 2012

2005 Datepicker control and dateformat

Hi, we have an installation of MSSQL reporting services where users
can select data based on date ranges. Since upgrading to 2005 we now
have a nice new Date picker control alongside textareas which accept
MSSQL datetime values.
This is all very nice but the date picker automatically formats the
date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
I
have checked the regional settings of both the browser/ server etc.
Scouring the Internet seems to point that this is a post SP2 problem
but there seems to be no fix other than making the datefields a type
of nvarchar and then converting them to dates in the Stored
Procedure.
If there really is no fix, how can I just disable this date picker
control? In 2000 people just entered the dates manually, this was
fine
but know there is a date picker control people are obviously going to
use it.
Thanks
RexOn Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> Hi, we have an installation of MSSQL reporting services where users
> can select data based on date ranges. Since upgrading to 2005 we now
> have a nice new Date picker control alongside textareas which accept
> MSSQL datetime values.
> This is all very nice but the date picker automatically formats the
> date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> I
> have checked the regional settings of both the browser/ server etc.
> Scouring the Internet seems to point that this is a post SP2 problem
> but there seems to be no fix other than making the datefields a type
> of nvarchar and then converting them to dates in the Stored
> Procedure.
> If there really is no fix, how can I just disable this date picker
> control? In 2000 people just entered the dates manually, this was
> fine
> but know there is a date picker control people are obviously going to
> use it.
> Thanks
> Rex
Aside from the workarounds you have attempted, that is also all I can
think of. If I understand you correctly, to remove the date time
picker in a specific report you would just select the Layout view ->
Report drop-down tab -> Report Parameters... and select the parameter
you want to remove the date time picker for and then change the Data
type: to something other than DateTime. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
> On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
>
>
> > Hi, we have an installation of MSSQL reporting services where users
> > can select data based on date ranges. Since upgrading to 2005 we now
> > have a nice new Date picker control alongside textareas which accept
> > MSSQL datetime values.
> > This is all very nice but the date picker automatically formats the
> > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > I
> > have checked the regional settings of both the browser/ server etc.
> > Scouring the Internet seems to point that this is a post SP2 problem
> > but there seems to be no fix other than making the datefields a type
> > of nvarchar and then converting them to dates in the Stored
> > Procedure.
> > If there really is no fix, how can I just disable this date picker
> > control? In 2000 people just entered the dates manually, this was
> > fine
> > but know there is a date picker control people are obviously going to
> > use it.
> > Thanks
> > Rex
> Aside from the workarounds you have attempted, that is also all I can
> think of. If I understand you correctly, to remove the date time
> picker in a specific report you would just select the Layout view ->
> Report drop-down tab -> Report Parameters... and select the parameter
> you want to remove the date time picker for and then change the Data
> type: to something other than DateTime. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant- Hide quoted text -
> - Show quoted text -
Hi Enrique, thanks for your help. I have found a fix which seems to
work so I'm posting here to help anyone in the future who comes across
the problem.
In the folder where Reporting Services is installed fin a file called
ReportView.aspx
e.g.
c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
\ReportServer\Pages\ReportViewer.aspx
Open up this file and add the following to the Page Directive
Culture="en-AU"
This seemed to solve my problem
Regards
Rex|||On Jul 5, 10:17 pm, Markus...@.gmail.com wrote:
> On Jul 6, 10:54 am, EMartinez <emartinez...@.gmail.com> wrote:
>
> > On Jul 5, 4:50 pm, Markus...@.gmail.com wrote:
> > > Hi, we have an installation of MSSQL reporting services where users
> > > can select data based on date ranges. Since upgrading to 2005 we now
> > > have a nice new Date picker control alongside textareas which accept
> > > MSSQL datetime values.
> > > This is all very nice but the date picker automatically formats the
> > > date to US format mm/dd/yyyy. We need it to be in dd/mm/yyyy format.
> > > I
> > > have checked the regional settings of both the browser/ server etc.
> > > Scouring the Internet seems to point that this is a post SP2 problem
> > > but there seems to be no fix other than making the datefields a type
> > > of nvarchar and then converting them to dates in the Stored
> > > Procedure.
> > > If there really is no fix, how can I just disable this date picker
> > > control? In 2000 people just entered the dates manually, this was
> > > fine
> > > but know there is a date picker control people are obviously going to
> > > use it.
> > > Thanks
> > > Rex
> > Aside from the workarounds you have attempted, that is also all I can
> > think of. If I understand you correctly, to remove the date time
> > picker in a specific report you would just select the Layout view ->
> > Report drop-down tab -> Report Parameters... and select the parameter
> > you want to remove the date time picker for and then change the Data
> > type: to something other than DateTime. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant- Hide quoted text -
> > - Show quoted text -
> Hi Enrique, thanks for your help. I have found a fix which seems to
> work so I'm posting here to help anyone in the future who comes across
> the problem.
> In the folder where Reporting Services is installed fin a file called
> ReportView.aspx
> e.g.
> c:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> \ReportServer\Pages\ReportViewer.aspx
> Open up this file and add the following to the Page Directive
> Culture="en-AU"
> This seemed to solve my problem
> Regards
> Rex
Very nice tidbit to know. So basically, that manually changed your
regional settings I guess.
Regards,
Enrique Martinez
Sr. Software Consultant