If I move my email server to a different server, and consequently a different IP address, but keep the same domain name, do I lose the work I've done to get whitelisted?
JohnB's questions
I know that VPU stands for Virtual Processing Unit (versus CPU), but what does that mean exactly? Is it just the new terminology for referring to processor resources in a virtual server versus a dedicated (physical) server?
My understanding is that VMWare can apportion cores in a processor across virtual servers. Can VMWare also allocate virtual cores that exist due to hyperthreading?
Is a VPU a shared core (i.e. shared across other hosting accounts)? Or does each VPS typically get 100% of its allocated VPU?
Is a Cloud Hosting VPS different from a traditional VPS from and end user's perspective?
I'm still a little fuzzy on these concepts, and I'm trying to evaluate different hosting plans.
On Internet Explorer Properties dialog, security level slider bar for internet zone is grayed out. Why?
(It seems to be stuck on the default level)
... after I add a column to a table. I've just started using 2008 R2 Management Studio, but I have a few years experience with 2005 Management Studio. Also, I am connecting to a 2005 instance of a database on a remote server.
- right-click on a column and select "Modify"
- supply new column name and datatype
- click "X"
- click "Yes" to save
- have to right-click -> "Refresh" on table, and then the new column shows up, but the hourglass never goes away! (see image below)
Why is this happening?
Running Win7 32-bit/Management Studio 2008 R2 32-bit. There could be other glitches too, I haven't used it enough yet.
(I've read a lot about 64-bit versus 32-bit OS/Apps, but this question is specifically in regards to databases.)
I'm trying to understand the pros and cons of 32-bit versus 64-bit databases, and namely, under what conditions that it starts to make sense to use 64-bit installations.
The database systems that I am interested in are: SQL Server 2008, MySQL, and PostgreSQL 9.0.
I have read that pre-9.0 versions of PostgreSQL only comes in 32-bit for Windows, and this article about running 32-bit PostgreSQL on 64-bit Windows clears up some of my confusion, but I'm looking for more info.
When would I benefit from using 64-bit databases (i.e. database size/disk space, available system memory, types of data sernarios that are known to benefit from it, which database engine being used, etc.)?
The databases that I am interested in are: SQL Server 2008, MySQL, and PostgreSQL 9.0.
In general, I am wondering which of those would "scale-up" the best. I have read that PostgreSQL used to scale-up better than MySQL, but that the difference has shrunk with newer versions of MySQL.
In addition to general information, I am also looking for advice for my specific situation:
I have a 64-bit SQL Server 2008 R2 Developer Edition database with 20 years of stock data and 2 years of options data. The hardware is Intel i7 Extreme with 6 cores, 12 GB RAM, 64-bit Windows 7.
The database is fairly large and intense calulations, such as moving averages, can take as long as 7 minutes. Furthermore, there's considerable disk activity even after the query is compete. I'm doing all the calculations in stored procedures right now.
My system is too slow and I am trying to improve its performance and efficiency. I am currently improving my data model and tweaking the software setup. Any suggestions?
Also, when should someone consider using MySQL Cluster? (Since I'm asking, I'm sure the answer is, "Not yours!")