At my organization, servers have a very cryptic name or a name where you can’t immediately tell the function. For instance, Amazon is the name of the SQL Server which our SharePoint uses as a back-end and Nile is the SQL Server hosting the databases for our HR application. This isn’t intuitive and it makes upgrading the servers a challenge because we always have to go back and touch the applications
2026-10-05
Wouldn't it be great if your HR folks only had to put in HR-SQL.mydomain.com for the database connection in their reports? They wouldn't have to remember it was on server Nile and they certainly wouldn't have to change their reports if you migrated their database from the Nile server to the server named Danube. In DNS there are two easy ways to do this.
2012-04-04
3,036 reads
By Steve Jones
Yesterday was the first day of sessions at the PASS Data Community Summit (after...
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...
Comments posted to this topic are about the item Pay for Performance, which is...
Jl. Jend. A. Yani No.224, Jatiwangi, Kec. Jatiwangi, Kabupaten Majalengka, Jawa Barat 45454
Jl. Raya R.Dengklok No.27, RT.049/RW.011, R.Dengklok Sel., Kec. R.Dengklok, Karawang, Jawa Barat 41352
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