Background

As you all know, Microsoft has already released SQL Server 2018 RC Version 1. So I wanted to give a try, and I decided to install the same. But at a stage in installation, I got an error which was not allowing me to continue further. I started to scratch my head. And finally I could find the solution. Here we will see that.

Fix to Rule “Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase” failed

Once you have started the installation, you can see a window as follows.

Installation Center SQL Server Start

If you have not installed SQL Server yet, you must select “New SQL Server stand-alone installation”, or you can upgrade by selecting “Upgrade from a previous version”. So we have started installing the things. When you are step away to finish everything once you have selected the features to add. You will be getting the error as follows.

—————————
Rule Check Result
—————————
Rule “Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase” failed.

This computer does not have the Oracle Java SE Runtime Environment Version 7 Update 51 (64-bit) or higher installed. The Oracle Java SE Runtime Environment is software provided by a third party. Microsoft grants you no rights for such third-party software. You are responsible for and must separately locate, read and accept applicable third-party license terms. To continue, download the Oracle SE Java Runtime Environment from http://go.microsoft.com/fwlink/?LinkId=526030.
—————————
OK
—————————

As it is mentioned in the link provided in the link, you can always download and install the Java SE from that link. This link will be redirected to http://www.oracle.com/technetwork/java/javase/downloads/index.html.

Java SE

Now we have an another option that to disable the Java SE from the features selected. For that go back to the feature selection.

Feature Selection Installation Center SQL Server

Now Uncheck the selection PolyBase query service for external data.

Feature Selection Installation Center SQL Server Uncheck Polybase Query Service

Now you can go ahead and click next. At last, you will get the success message.

Installation Center SQL Server Success

Hooray, we have successfully installed our new version of SQL Server. That’s fantastic right? Have a happy coding.

Conclusion

Did I miss anything that you may think which is needed? Could you find this post as useful? I hope you liked this article. Please share me your valuable suggestions and feedback.

Your turn. What do you think?

A blog isn’t a blog without comments, but do try to stay on topic. If you have a question unrelated to this post, you’re better off posting it on C# Corner, Code Project, Stack Overflow, Asp.Net Forum instead of commenting here. Tweet or email me a link to your question there and I’ll definitely try to help if I can.

Kindest Regards
Sibeesh Venu

Hi All, How are you today? In this article we will see a solution for a fix that we usually encounter when you work in Microsoft SQL server. The error message will be “Saving changes is not permitted,The changes you have made require the following table to be dropped and re-created. You have either made changes to the table that can’t be re-created or enabled the option Prevent saving changes that require the table to be re-created.”. Let us see how we can solve this issue. I hope you will like it.

Background

As the error message says, it is because of you have enabled the option Prevent saving changes. Now we will see how we can disable that option in SQL Server Management Studio. Before going through the fix, we will see teh screenshot of the error.

Steps to follow

To fix this issue, you need to follow some certain steps. We will explain that here.

Step 1

Go to Tools menu and click on options.

Step 2

Now you can see a window is opened as follows. You can see some settings there. No need to change anything in that.

Step 3

Now go to Designers menu and click on “Table and Database designers”

Step 4

It is time for changing the settings. As you can see there is a check box which is captioned as “Prevent saving changes that requires table re-creation” . Just uncheck that and click OK.

That is all. Now if you try to save that table, you won’t be facing above mentioned issue. Have a happy table designing.

Conclusion

I hope you will like this article. Please share me your valuable thoughts and comments. Your feedback is always welcomed.

Thanks in advance. Happy coding!

Kindest Regards
Sibeesh Venu

Hi All, I hope you are fine. We all are using SQL parameter in our application right?Yeah it is a good way to restrict the Injections are hijacks. But still if you pass those parameters in the right way, you will face lots of problems. In this article I am going to share you such an Issue. I hope you will like it.

Background

Morning I was working in a grid control which editable, and I selected a row to edit and started editing. In a date field I edited the date and clicked update button. I was expecting an output result as “Successfully updated”. But it didn’t happen. Instead it throws an error. “SqlDateTime Overflow, Must be between”

Using the code

To resolve this issue, first you must understand the root cause for this. I was passing the parameters as follows.

[csharp]
SqlParameter[] myParam = new SqlParameter[3];
myParam[0] = new SqlParameter("@name", myObject.name);
myParam[1] = new SqlParameter("@ValidFrom", myObject.hjcValidFrom);
myParam[2] = new SqlParameter("@ValidTo", myObject.hjcValidTo);
[/csharp]

When I run my application with above code, I got the following error.

So what is the fix/solution?

I changed the parameter as follows.

[csharp]
SqlParameter[] myParam = new SqlParameter[3];
myParam[0] = new SqlParameter("@name", myObject.name);
myParam[1] = new SqlParameter("@ValidFrom", myObject.hjcValidFrom.ToString("MM/dd/YYYY"));
myParam[2] = new SqlParameter("@ValidTo", myObject.hjcValidTo.ToString("MM/dd/YYYY"));
[/csharp]

That solved the issue. Simple right?

Some other case

There are dome other cases you may get this error if you use the codes as follows.
[csharp]
SqlParameter[] myParam = new SqlParameter[3];
DateTime myDate=new DateTime();
myParam[0] = new SqlParameter("@name", myObject.name);
myParam[1] = new SqlParameter("@ValidFrom", myDate);
myParam[2] = new SqlParameter("@ValidTo", myDate);
[/csharp]

What you have to do all to fix this issue is just take the now property value from your date time object and pass it your parameter.

[csharp]
SqlParameter[] myParam = new SqlParameter[3];
DateTime myDate = DateTime.Now;
myParam[0] = new SqlParameter("@name", myObject.name);
myParam[1] = new SqlParameter("@ValidFrom", myDate);
myParam[2] = new SqlParameter("@ValidTo", myDate);
[/csharp]

Conclusion

I hope you enjoyed reading and found this useful. Please share me your valuable feedback. For me it matters a lot.

Kindest Regards
Sibeesh Venu