Today we have a guest editorial from Andy Warren as Steve Jones is at SQL Bits.
I learned databases back in the days of DOS and DBF files. If you ever worked with dBase III or anything that used the DBF format you wound up with a folder full of various files. I remember trying out Access v1.1 (May 1993 for those who wondered). It was I think the first Windows database I had used and I remember thinking how nice it was to have all the “files” in a single container, the MDB. I went on to use it a lot. I built a couple apps that used it for a data store, I used it a lot for ad hoc reporting and data entry/fixing, and I worked at a company that used it as their primary ETL solution.
Later I moved on to SQL Server 6.5 and 7.0. I remember learning to create indexes in SQL and being struck that I had to give them names - in Access you just entered the columns, no name required. That was a worthwhile tradeoff just to be through with doing the compact/repair operation that seemed to be required all too often in Access.
The strength of Access has been that it made databases approachable and affordable - both important attributes for the beginner or for the very small business trying to find a way to solve relatively small data problems. Access also made it easy to build a data driven “application”, perhaps at the time second only to FoxPro, and perhaps superseded now by Lightswitch, though I haven’t tried it to know for sure. Ease of use matters, something we can see clearly in Excel.
The pain of Access comes when the database gets too big, too slow, or the app just gets too unwieldy. Then we as DBA’s and developers get called in to “fix” the problem and the fix often requires moving data to SQL and substantial changes or replacement to the code along with it. Access. I’ve never minded that work - upgrades and refreshes are a big part of what we do, all across the enterprise. Which isn’t to say I haven’t seen horrible things done in Access that were truly a pain to figure out and upsize.
Maybe it’s because I ‘grew up’ with Access but I don’t share the disdain that many have for it. Access is the logical next step when a user needs to move beyond Excel.They may not normalize as much as we would like, they probably have a lot of cursor-ish looking code, but they are making that first step to working with data. That’s ultimately good for the business and good for us, even if it means we have to step in to do some clean up sometimes.
SSIS was designed to be extensible.Although you can create tasks that will take data from a wide variety of sources, transform the data is a number of ways and write the results a wide choice of destinations, using the components provided, there will always be occasions when you need to customise your own SSIS component. More »
Get a head start evaluating SQL Server 2014 - guided by two experts who have worked with the technology from the earliest beta. Based on Community Technology Preview 2 (CTP2) software, this guide introduces new features and capabilities, with practical insights on how SQL Server 2014 can meet the needs of your business. Get the early, high-level overview you need to begin preparing your deployment now.
A primary key is not an index but a logical constraint, to indicate the default candidate key to be used to select particular rows of the table. Any candidate key must be unique, and must not allow nulls.
For a table to be relational, any scalar value must be addressable by specifying the table, column and the key value(s) of the containing row. This key, often referred to as a candidate key, defines a set of one or more columns that together can distinguish individual rows in a table.
The method used to enforce these requirements can vary between implementations of RDBMS. The most obvious method is a combination of unique index and NOT NULL constraint.
Unless you specify a unique nonclustered index to enforce this primary key, SQL Server will automatically create a unique clustered index on the column or columns unless a clustered index on the table already exists. Because the primary key column(s) cannot allow NULL values all columns are set to NOT NULL. You cannot assign an existing index to enforce a primary key.
Use a Like in a Replace Cast sentence?
- Hi, i would appreciate suggest the SQL sentence, thanks
CREATE TABLE [dbo].[instructions](
[site_no] [int] NOT NULL,
[instructions] [text] NULL
Select top 3 * from instructions
Datetime conversion issue
I would be very grateful for your help with the following query. All source and target date fields are defined...
Encrypt SSN Example (TDE)
- Does anyone have an example on encrypting a SSN Field using TDE?
Any help would be greatly appreciated.
not able to attach Database. getting file path error
- TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'xyz'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.2218.0+((SQL11_RTM_GDR).120612-1250+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&
- I know this is the wrong forum to post but I have no idea where to post and this is...
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.