[MSSQL] Time & date Synchronization
This is my first post here in coders paradise section. As the title goes I read the rules but it seems that coders section only support php, mysql, c++ anyway. How do you sync the time and date for mssql to your current time? im hosting server for online game I created item with expiration but when i tried to open it, it expires right away as soon as i login in the game and how do you secure the server mssql for hackers attack? Thank you and more power to you guys! Tnx again in advanced.
Re: [MSSQL] Time & date Synchronization
Quote:
Originally Posted by
deadfox
This is my first post here in coders paradise section. As the title goes I read the rules but it seems that coders section only support php, mysql, c++ anyway.
This section is for any coding language- mark-up, scripting, or programming- this includes databases. So MSSQL is welcome, too.
Quote:
Originally Posted by
deadfox
How do you sync the time and date for mssql to your current time?
MSSQL uses the System Time it's configured on. So you just edit the system time.
Here's a guide if you're trying to get the right Offset for user's time-zones
Timezone Offsets With Sql Server - Revisited | Mike Gleason jr's Blog
I may have misunderstood the question- is SQL Server running on your Hosting box, or somewhere off in the Internet?
Quote:
Originally Posted by
deadfox
im hosting server for online game I created item with expiration but when i tried to open it, it expires right away as soon as i login in the game
Sounds like it could be a problem in the application layer rather than the database layer.
Can you post the server-side code you're using for this particular issue?
Quote:
Originally Posted by
deadfox
and how do you secure the server mssql for hackers attack?
There's no "1-step approach" to securing your web applications. The sad truth is, your server is connecting to potentially, millions of users, and there's no way to protect against certain attacks- especially the ones that rely solely on anonymous visiting rights (such as DDos). But that doesn't take away from the fact you should do your best to stay secure, and code securely.
The best way to implement security is to do so as you're coding your server-side application layer.
At least that's the most important part. Common threats are when you inadvertently give the user access to your file-system, a server-side function such as eval, inject HTML or JavaScript onto your web-page, the possibility to execute queries or sub-queries on your database, and many more possibilities can come up the more you add to your server/application "willy-nilly". By willy-nilly, I mean, getting things from the web like tools or widgets made in PHP or JavaScript, or putting up images before scanning them, etc- things can contain malicious code, and web-developers are far less cautious then they should be when adding extensions, libraries, or what-have-you to their PHP or JavaScript. Something as simple a GIF image can cause serious harm to your server using the PHP scripting language.
You can look at this guide to try and stay secure as possible:
Security tips for web developers
And here's your MSSQL security
http://www.windowsecurity.com/articl...-Security.html