Linq to Sql (unfortunately) is designed to only connect with SQL Server. If you have other database types, you may want to give Linq to Entities a go. There are several videos/blogs on the topic.
Depending upon the needs of your application, an understanding of underlying ADO.NET can't hurt either.
As to your original question (dragging and dropping), how good that is will be determined by how good the data design is. For well designed Relational Database Management Systems, I don't see the harm of using a drag'n'drop CRUD/ORM code generation tool like Linq to SQL/Linq to Entities. It handles the mundane tasks of data access and persistence, freeing you to focus on details like the business logic of the application.