Static data is often required for the basic functioning of a database and any dependent applications. Therefore, it's vital that we can track this static data to understand how, when, and why it changed, and that we include any static data changes in our database deployments. Flyway Enterprise will now do both tasks automatically.
2023-04-24
We may need to share our Python desktop or console applications with business users or deploy these applications to multiple machines. However, there are some challenges in the delivery of Python applications.
2023-04-24
Steve takes a look at go-sqlcmd, the newest evolution of the sqlcmd command line tool.
2023-04-21
7,882 reads
Sometimes you might have your data within a SharePoint list, and you would prefer this dataset to be within a SharePoint folder instead for reasons like reporting in Power BI or Excel. You need to be able to move the data automatically from the SharePoint list to the SharePoint folder.
2023-04-21
The Tab Coloring component of SQL Prompt’s SSMS Tab management could save you from accidentally doing something apocalyptic on a production server, ever again.
2023-04-21
Firebase is a NoSQL database, while Supabase is a relational database. The type of software you’re constructing determines which database is best for your project.
2023-04-19
In 2023, connect, share & learn with like-minded peers, speakers, and industry leaders during the full week of data celebrations. Summit happens in person, from November 14th to 17th in Seattle. Check out the blog post to learn more.
2023-04-19
Learn how to create a copy of an existing database without any data using Integration Services.
2023-04-17
3,636 reads
Mistakes occasionally happen. Occasionally, you make some ill-judged 'refinements' to working code and now just wish you could rewind your tab back in time an hour and forget the whole sorry episode. Now and again, SSMS just conspires against you and crashes unexpectedly, and you lose all your currently open query tabs, some of which you hadn't saved. SQL History offers a useful safety net in the event of any of these unfortunate events.
2023-04-17
As much as we tell people to use SCHEMABINDING and avoid SELECT *, there is still a wide range of reasons people do not. A well-documented problem with SELECT * in views, specifically, is that the system caches the metadata about the view from the time the view was created, not when the view is queried. If the underlying table later changes, the view doesn't reflect the updated schema without refreshing, altering, or recreating the view. Wouldn't it be great if you could stop worrying about that scenario and have the system automatically keep the metadata in sync?
2023-04-17
By Steve Jones
AI is a big deal in 2026, and at Redgate, we’re experimenting with how...
By Steve Jones
Another of our values: The facing page has this quote: “We admire people who...
By Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
Comments posted to this topic are about the item No Defaults Passwords Ever
Hi, We have low latency high volume system. I have a table having 3...
Comments posted to this topic are about the item The Long Name
I run this code to create a table:
When I check the length, I get these results:
A table name is limited to 128 characters. How does this work?