Posts

Disadvs of NoSql DBs

  Disadvantages of NoSQL  DBs 1. The Death of the "True" Join In NoSQL, native cross-collection relationships do not exist . In an RDBMS, you normalize data across tables and link them using foreign keys. MongoDB: While you can use the $lookup aggregation stage to perform a left-outer join, it is highly resource-intensive. If your query filters heavily on non-indexed joined fields, performance degrades rapidly. Cosmos DB: It does not support joining data across separate containers natively. To join data, you must self-join within the same item, query collections separately in application code, or completely change your architecture to de-normalize your data. 2. Duplicate Data and Memory Bloat NoSQL is to duplicates data across multiple documents. Data Duplication: If a user updates their username, your application code must hunt down and update that string across every single order, comment, and document where it was copied....
Post a Comment
Read more

Break old version control links

Break old version control links If need to break old version control links, when you move your source control solution: 1. Files and Folders to Delete Search your entire solution for these files and delete them: *.vssscc and *.vspscc (Visual Studio Team Foundation / TFS binding files) *.scc and vssver.scc / vssver2.scc (Visual SourceSafe files) The hidden .vs folder in the root solution directory (stores local user options and caches)    2. Edit the Solution File ( .sln ) Open your .sln file in a plain text editor like Notepad. Find and remove the entire block starting with GlobalSection(TeamFoundationVersionControl) = preSolution or GlobalSection(SourceCodeControl) = preSolution down to EndGlobalSection . Save the file.    3. Edit the Project Files ( .csproj ) Open each individual project file (e.g., *.csproj ) in Notepad.  Look for XML tags starting with Scc inside the <PropertyGroup> tags and delete them: SccProjectName SccLocalPath SccAuxPat...
Post a Comment
Read more

Adjusting DLLs in VS

Adjusting DLLs in VS    I had an old Visual Studio project where I had a mismatch of old v12.1 third-party Dlls in the deployment folder but had v13.1 references in the code of the project. So I needed to downgrade, however most of the time you are modernizing instead. 1. The Project Files  (.csproj or .vbproj) Open the files in a text editor and look for the <Reference> tags.  Change the reference names from DllName.v13.1 to  DllName.v12.1 . Change from  Version=13.1.x.x to  Version=12.1.x.x  matching your actual DLLs. Verify  <HintPath> points to your local Lib folder where you put the renamed v12.1 DLLs. 2. Configuration Files  (web.config or app.config) Third parties often registers their HTTP handlers, modules, and compilation assemblies here. Replace all instances of v13.1 and Version=13.1.x.x with 12.1 equivalents. 3. The License File  This  licenses.licx   file lives inside your project's Prope...
Post a Comment
Read more