Serverless – The provided execution role does not have permissions to call CreateNetworkInterface on EC2

Issue – while deploying Serverless Lambda (sls deploy command ) function I got below error message An error occurred: EsLambdaFunction – The provided execution role does not have permissions to call CreateNetworkInterface on EC2 (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: xxx). Resolution – In order to resolve the issue; I have… Read More Serverless – The provided execution role does not have permissions to call CreateNetworkInterface on EC2

Replication – Agents Job Location

Issue – Where Replication Agents job Locate Resolution – While troubleshooting replication issue; it’s always good to know which server have which job. In transnational replication scenario. Snapshot agent Log Reader agent Distribution agent If Publisher and Distribution Server is same and you have configured Push subscription; all the job reside Publisher\Distributor server. If Publisher and… Read More Replication – Agents Job Location

Replication Issue – Cannot execute as the database principal because the principal “dbo” does not exist, this type of principal cannot be impersonated, or you do not have permission.

Issue – Replication Log Reader agent was failing with below error messages. 2018-04-24 19:33:07.854 Status: 32768, code: 53044, text: ‘Validating publisher’. 2018-04-24 19:33:07.873 Status: 4096, code: 20024, text: ‘Initializing’. 2018-04-24 19:33:07.873 The agent is running. Use Replication Monitor to view the details of this agent session. 2018-04-24 19:33:07.879 Status: 0, code: 20011, text: ‘The process… Read More Replication Issue – Cannot execute as the database principal because the principal “dbo” does not exist, this type of principal cannot be impersonated, or you do not have permission.

Reading\Writing Different file format in HDFS by using pyspark

Issue – How to read\write different file format in HDFS by using pyspark File Format Action Procedure example without compression text File Read sc.textFile() orders = sc.textFile(“/user/BDD/navnit/data-master/retail_db/orders”) Write rdd.saveAsTextFile() orders.saveAsTextFile(“/user/BDD/navnit/saveTextFile/orders”) sequence File Read sc.sequenceFile(ordersSF = sc.sequenceFile(‘/user/BDD/navnit/saveSequenceFile/orders’) Write PipelinedRDD.saveAsSequenceFile() ordersKV.saveAsSequenceFile(‘/user/BDD/navnit/saveSequenceFile/orders’) Avro file Read sqlContext.read.format(“com.databricks.spark.avro”).load() orders = sqlContext.read.format(“com.databricks.spark.avro”).load(“/home/BDD/navnit/orders/”) Write dataFram.write.format(“com.databricks.spark.avro”).save() orders.write.format(“com.databricks.spark.avro”).save(“/user/BDD/navnit/saveAvroFile/orders”) Parquet File Read sqlContext.read.parquet() ordersParquet =… Read More Reading\Writing Different file format in HDFS by using pyspark

Cannot resolve the collation conflict between “xxx” and “xxx” in the equal to operation

Issue – Customer was getting below error when he was running any query. Msg 468, Level 16, State 9, Line 36 Cannot resolve the collation conflict between “SQL_Latin1_General_CP1_CI_AS” and “SQL_Latin1_General_CP1_CS_AS” in the equal to operation. Back ground – Table was part of replication and when he was running query on subscribe he was getting collation conflict… Read More Cannot resolve the collation conflict between “xxx” and “xxx” in the equal to operation

Login failed for user ‘xxx’. Reason: Server is in single user mode. Only one administrator can connect at this time.

Issue – Login failed for user ‘xxx’. Reason: Server is in single user mode. Only one administrator can connect at this time. Cause – Ensure SQL Server is not running in Single user mode by checking start-up parameter. if you see -m; it mean your SQL is running with single user mode. -m : Starts an… Read More Login failed for user ‘xxx’. Reason: Server is in single user mode. Only one administrator can connect at this time.

The target database, ‘xxx’, is participating in an availability group and is currently not accessible for queries.

Issue – The target database, ‘xxx’, is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary… Read More The target database, ‘xxx’, is participating in an availability group and is currently not accessible for queries.

Microsoft Contoso BI Demo Dataset for Retail Industry

Today, I was working on demo where I wanted to have test dataset for Retail db and after some googing I found MS has it’s own database and here are details – The Contoso BI Demo dataset is used to demonstrate DW/BI functionalities across the entire Microsoft Office product family. This dataset includes C-level, sales/marketing,… Read More Microsoft Contoso BI Demo Dataset for Retail Industry

The transaction log for database ‘XXX’ is full due to ‘LOG_BACKUP’

Yesterday, one of my client send me email stating she is not able to run any query against database. she was getting below error message – The transaction log for database ‘xxx’ is full due to ‘LOG_BACKUP’ From error message it’s look like transaction log full issue hence I looked for db property and found… Read More The transaction log for database ‘XXX’ is full due to ‘LOG_BACKUP’