Skip to main content

Posts

How to Create Read-Only User in MySQL using workbench

Friends, Till now I haven’t got chance to vote in any election for PM or CM. This month everywhere talking about elections and here I am busy with my work connect-share-discover with database and applications..  Today I want to share How to Create Read-Only User in MySQL using workbench. First Go to Users and Privileges option from Workbench Managements Tab. Click on Add account and give account name and their respective password, after that apply. In Users and Privileges box there are 2 other tabs, Administrative Roles and schema privileges. Administrative Roles is Similar to Fixed Server roles of SQL Server. Schema privileges is schema level authorization process. Select Schema privileges and click on Add Entry. Then a Dialog box will come with schema available in server. Now select any schema which privilege we have to configure. After that give the appropriate rights which we have to give. As I have selected on select. Finally click on Apply.

Dont worry if SSMS not support attaching FILESTREAM enabled databases

SQL Server 2005 introduced the unstructured data types VARCHAR (MAX), NVARCHAR (MAX) and VARBINARY (MAX). And later on File stream features came with 2008. We are using SQL Server version 2012 and unfortunately I would like to say to Microsoft doesn’t given option to attach File-stream Enabled Database from SSMS. Mostly this requires when trying to migrate DB or system or doing some DR activity or maintenance activity. If you will try to attach from SSMS then it may give some errors like below … TITLE: Microsoft SQL Server Management Studio ------------------------------ An error occurred when attaching the database(s).  Click the hyperlink in the Message column for details. ------------------------------ BUTTONS: OK ------------------------------   But don’t worry just try below query to re-attach db.. USE [master] GO CREATE DATABASE <DBNAME> ON ( FILENAME = N'LOCATION\name.mdf' ), ( FILENAME = N'Location\name.ldf&#

SQL server day 17th January 2015

I enjoyed a lot my birthday with SQL Server Community.. Luckily this year on 17 th Jan SQL Server Day organized by SQL Server geeks. SQLServergeeks is asia’s biggest SQL Server community and I am one of active member here since 3 years. There was no cacke sake, no party just learning and networking with people … Agenda was: - SQL Azure Introduction of cloud based RDBMS with SQL Azure . By Ahmed sir   Configuration of azure for our environment . #LiveDemo by Ahmed sir Backup-Restore with managed backup . #LiveDemo by sarabpreet sir Discussion about great features of #sqlazure. By sarabpreet sir We learned and enjoy a lot with 100’s of DBA who came from different companies to make successful SQL Server Day 2015. In the last big announcement made for SQL Server Geeks. They announced for Annual Summit 2015 on August 27, 28, 29, 2015 in Bangalore at NIMHANS Convention Center. And Pre-Cons on Aug 26. https://www.facebook.com/groups/thesqlgeeks/permalink/8339

Storing BLOB Data: Data Base vs NTFS File System

BLOB/Image/Videos are unstructured data. RDBMS like SQL Server is made to store relational data. File stream is new feature of SQL Server since 2008 to store large data. This is not always the best solution to store images on db. Store the pictures on the file system and picture locations in the database. My previous experience is also saying. Why? Because...

Database 'distribution' cannot be opened. It has been marked SUSPECT by recovery

Last week I faced an error on testing environment while right click on my subscriber and article property.    ------------------------------ Database 'distribution' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server error log for more information. (Microsoft SQL Server, Error: 926) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.5058&EvtSrc=MSSQLServer&EvtID=926&LinkId=20476 ------------------------------

MySQL showing Wrong Time due to time zone

Last Month Faced an Issue on one of MySQL DB Server. System Date was showing wrong while System time was correct. I compared both time like below: