Database monitoring is an essential part of database development and testing because it will reveal problems early and allow you to drill down to the root cause, as well as look for any worrying trends in behavior of the database, when under load. If you are delaying doing this until a database is in production, you're doing it wrong.
There is more than one way to work with SQL Server stored procedures from within a .NET Application. However, when using parameters, in order to avoid exposing your code to "SQL Injection" vulnerabilities, there is a certain way based on which you should write your code.
Steve isn't sure that AI is that helpful with data tasks. It can be, but likely in specific areas rather than helping us with everything and taking our jobs.
Conferences have been a part of Steve's career for a long time. He talks about how he'd taken advantage of the opportunities he's had.
There are several techniques available to import and export data for SQL Server. In addition, there are free SQL tools and utilities available that might be helpful for specific use cases. In SQL Server Integration Services (SSIS), we can use a Flat File Source to load Text/CSV files. Despite this, I would like to demonstrate how to import Text/CSV files using the Script Task.
In coming up with a strategy for managing test data, first you need to understand what the many test requirements are likely to be for the particular database you are developing. Next, you need to create all the different categories of test data required to suite test requirements and, finally, work out how to manage it in a way that allows a test-driven approach to development.
Read more in this latest article from Phil Factor
Using code to help you write code is a time honored tradition in software development.
Time has brought clarity for changes which could and should have been provided by its instigators. We compare a change where clarity was sought to those that were chaotic and the approaches that were taken at their two poles.
An important aspect of building and managing a database is organizing the objects within your database. You may have tables that support different functions, for example, a schema for warehousing operations and another for sales. Some logins may need access to some tables, but not others. You might want to isolate one set of objects within a database from other sets of objects. All of this, and more, can be accomplished using schemas within a database and PostgreSQL supports the use of schema for just these types of functions.
This month’s blogging party is hosted by Jeff Ianucci – his challenge is to...
As for me, I'll keep writing whenever time permits. I don't expect every post...
By Steve Jones
This is an interesting invitation this month. Jeff Ianucci is a new host, and...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Switching Schemas I
Comments posted to this topic are about the item Enforcing Unique Customer Emails When...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers