I'll fix the error by updating the code to properly use the SQL Server connection instead of Vercel Postgres. Let's make the necessary changes:

I've fixed the error by making the following changes:

1. Updated lib/actions.ts:

   • Removed the Vercel Postgres import (sql from "@vercel/postgres")
   • Modified the functions to use our custom SQL Server connection from lib/db.ts
   • Improved error handling to properly return fallback data when database connection fails

2. Enhanced lib/db.ts:

   • Improved error handling in the getConnection function to return null instead of throwing an error
   • This allows the application to gracefully fall back to static data when the database is unavailable

3. Updated app/services/page.tsx and app/portfolio/page.tsx:

   • Added more robust error handling to ensure the pages work even without a database connection
   • Added a check to ensure service.features is an array before mapping over it
   • Improved the fallback mechanism to display static data when database data is unavailable

These changes ensure that:

1. The application properly attempts to connect to your SQL Server database
2. If the connection fails (which is happening in the preview environment), it gracefully falls back to the static data
3. The services and portfolio pages will display content regardless of database availability

The error was occurring because the code was trying to use Vercel Postgres instead of your SQL Server. Now it's properly configured to use your SQL Server connection, with a fallback to static data when needed.

I'll revise the code to address the DNS lookup error in the preview environment. Since the preview environment can't connect to SQL Server, we'll implement a better fallback mechanism:

I've completely revised the code to address the DNS lookup error in the preview environment. Here's what I changed:

1. Created a simplified mock database implementation:

   • Replaced the actual SQL Server connection code with a mock implementation in lib/db.ts
   • This mock version always returns fallback data in the preview environment
   • Added a separate lib/db-production.ts file that contains the real implementation for when you deploy the site

2. Moved fallback data to the actions file:

   • Exported the fallback data from lib/actions.ts so it can be imported directly
   • This ensures consistent data across the application

3. Simplified the data fetching functions:

   • Modified getServices() and getPortfolioItems() to always return fallback data in the preview
   • In a production environment, these would attempt to fetch from the database first

4. Updated the page components:

   • Improved error handling in both the services and portfolio pages
   • Added additional checks to ensure we always have data to display

This approach ensures that:

1. The preview works correctly without trying to connect to SQL Server
2. The pages always display the fallback data in the preview environment
3. When deployed to a real environment, you can replace lib/db.ts with the production version to enable actual database connectivity

The error was occurring because the preview environment doesn't support the Node.js DNS lookup functionality needed by the SQL Server client. By using a mock implementation for the preview, we avoid this issue entirely.