new SQL considerations

we have 2 SQL server running in a Cluster mode. The DB is located on a storage.
The servers and the storage are very old now and we want to buy new hardware and upgrade.

Now my DB is on a storage but I want to change this.
I want to buy to servers and want to have the DB´s directly on the servers, because of performance.
I want to create different Raid Sets for TempDB, DataBase FIles and Logfiles.
Can you help me which mode is recommended and useful ?

this is a nice link and I want to go this way.
On my server I want to have disks for the TEMP-DB, I will go for SSD´s.
The Disks for Data and the Disks for the logfiles will have different Raid Sets, right, but no SSDs ?

What is the name of the cluster which I am gonna use with 2 servers and no storage in the back ?
And is it really a secure way to have my DB always online ?

Do you want to create a SQL Server instance in a cluster without shared storage?
And you are complaining about actual performance?
Looks like you has your mind set on this solution so best thing to do it's let you go through this so you can see by yourself how good is this solution compared to the previous one that's already working.

I can understand the SQL Server in physical server part but not the data and transaction log files in local disks.
If the new cluster won't work with shared storage means that they will work with SMB (a Microsoft protocol for network file sharing) and I can't see any advantage on that.

Not me but your SQL Server experts. If it was me I would let them in a storage solution.
If you or your SQL Server colleagues wants to use the files in a local storage then I will suggest using AlwaysOn instead of the classical cluster solution.

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

I was also thinking about SQL2014.
Here the whole DB is in RAM located. But just 128 GB RAM maximum with the STD version.

You need to think in SQL Server 2014 if you want to use the In Memory OLTP feature. 128GB may be enough since you can chose which tables you want to put all in memory and which ones do you want to leave in disk.

For my customers I need just one access Point to the DB, like the old cluster.
With AlwaysOn, do I have the same ?

That's a new info. If you are going to configure AlwaysOn then the cluster will be only for the Operating System, right?
I was more concerned about the High Availability and also the security that a storage solution usually has. For me that's more important than performance. But I can also understand the costs side. You need to balance it and chose what's more important for you.

JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.

This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.

Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed