Sep 22, 2016
Loading...
seen from Australia
seen from Malaysia
seen from United States
seen from China
seen from Russia
seen from Malaysia
seen from China
seen from Malaysia
seen from United States
seen from United States
seen from Germany
seen from Romania
seen from United States
seen from Yemen
seen from Singapore
seen from Germany
seen from United States
seen from United States
seen from Malaysia
seen from Netherlands
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Microsoft SQL Server 2016 and Azure SQL Database / Database Engine Permissions Poster #azurejp
Permissions (Database Engine)
(Permissions (Database Engine)から)
複雑過ぎる。
New Database scoped Configurations
#New Database scoped Configurations #SQL #Azure #SQLAzure @SQLChamp MS introduced new Database scoped configurations in SQL Azure (V12) and SQL Server 2016; Need for new Database Scoped Configurations Have you ever faced a situation where one of the database requirements are totally different from other like MAXDOP settings and you wanted to set a different MAXDOP for a single DB; or you wanted a feature which can keep such Primary and secondary database configurations in sync. MS is listening and they introduced Database Scoped Configurations and you can change them with this DDL statement: Alter Database Scoped Configuration. This was a much needed enhancement. Here's a list of Database scoped configurations which are now available on DB level. These are not new configurations, but now you can also configure these options at the database level rather than the server level. So imagine you are planning to consolidate servers on a single instance, but earlier you were not able to do it because of different needs of such configurations, http://www.sqlchamp.com/2016/06/database-scoped-configurations/230 http://www.sqlchamp.com/2016/06/database-scoped-configurations/230
AT Time Zone – Convert timezone directly using SQL
AT Time Zone – Convert #timezone directly using #SQL #azure @SQLCHAMP Globalization brings new opportunities and enhance economic growth to any business, but along with all the goodness it also brings complexity to manage different time zones. One has to be always on toes to match different times. but what if you've got an application\code where you have to convert timezone within SQL Server data? If you are using SQL Azure Databases or SQL Server 2016 you don't have to worry about this trouble because Microsoft introduced this brand new function to make things easy for you: AT TIME ZONE; AT Time Zone This function converts an inputdate to target time zone as per your wish, isn't it cool. I am loving it, it simplified too many things. Now I don't have to write code\use dlls to convert date time – DST was the biggest issue and this function simply takes care of DST on its own. http://www.sqlchamp.com/2016/06/at-time-zone/206 http://www.sqlchamp.com/2016/06/at-time-zone/206
Find End-Of-Month (EOMONTH) date from SQLServer
Find End-Of-Month ( #EOMONTH ) date from #SQLAzure #SQL Hi Friends, have you ever struggled to find the end of the month date; I know its not a big deal you can get it from Calendar but what if you need that date for some business logic of yours? May be for Invoice processing or some other scheduling within SQL Server and you want to store \process that date? Yes, it becomes time consuming. Thankfully SQL Server has this (EOMONTH) datetime function which can be used to calculate the end of the month date automatically for any given month. Function:EOMONTH (this functions is available in Azure SQL Databases & starting SQL Server 2012) this takes two parameters http://www.sqlchamp.com/2016/05/eomonth-sql/199
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Know these restrictionslimitations before moving to SQLAzure
Know these restrictions #limitations before moving to #SQLAzure #SqlChamp As we already discussed SQLAzure is an offering under Microsoft Azure umbrella as PaaS (Platform as a service) & there are limitations of using SQLAzure (SQLDatabase) over SQLServer in Azure VM (or on-premise SQLServer) I am listing down all the limitations under specific headings which will help you prepare accordingly and decide before shooting the arrow (Making the switch). Make sure you read the detailed difference between both offerings so that you understand it better. The Limitations of SQLAzure are as follows: Troubleshooting & Audit related Limitations Eventing: events, event notifications, query notifications Read More at http://www.sqlchamp.com/2016/04/sqlazure-limitations/166 http://www.sqlchamp.com/2016/04/sqlazure-limitations/166
How to create a new #database using #SQLAzure Hi Friends, In the last post we summarized the main differences between running your workload on SQLAzure and SQLServer on Azure VM. In this post we’ll see how to create a new database using SQLAzure? You must have an Azure subscription in order to start provisioning your own databases using SQLAzure, If you don’t have one but still want to learn and explore Azure– refer to my Pro-Tip to get a free trail limited subscription of Azure. Let’s create the database: Step-by-Step Login to Azure portal Read More at http://www.sqlchamp.com/2016/04/new-db-sqlazure/157 http://www.sqlchamp.com/2016/04/new-db-sqlazure/157
The unintuitive Could Not SQLExecDirect RODBC Error and solution
So I've got this non sense error while using sqlSave
[RODBC] ERROR: Could not SQLExecDirect 'CREATE TABLE ... blah blah blah
Here is the short story, and it is important to talk about the setup, I'm using RODBC and FreeTDS to connect to the SQL Azure database. Remember it is SQL Azure database. First, it does not play nice with the database without a cluster key, or a key, so what need to do is addPK = T or longer version addPK = TRUE
Solution #1. two steps approach
This will help create the proper table structure, however it'll still fail you. Don't worry. Now what we need to do is to append the data sqlSave(ch, USArrests, addPK = T) It will tell you the error, then what you need to do next is to append the data sqlSave(ch, USArrests, tablename = 'USArrests', append = T) Now you ready to hail or shout hurray?!
Solution #2.
That is not me, I'm lazy, it should be done in one command
That solution does not seem to be making sense, here is the better version
sqlSave(ch, cust, tablename="dbo.customers", safer=F, addPK=T)
Safer = F does the trick. not sure if this is the bug from FreeTDS or RODBC sqlSave function.
======
If you actually read this far, congratulations, you found the solution - INSTALL Microsoft SQL Server ODBC Driver
http://www.microsoft.com/en-us/download/details.aspx?id=36437